Hands-on – Learn how to Backup and Restore in Azure App Service

Backing up and restoring an Azure App Service is an essential practice for ensuring that your application and its data are safe in case of issues like accidental changes, data corruption, or other disruptions.

Azure provides built-in tools to make backup and restore processes easier to manage.

Here's everything you need to know about Backup and Restore for your App Service.

Backup Overview

Azure App Service provides an easy way to back up your web app, including the web app's content, configuration, and database (if integrated with a supported database, such as Azure SQL Database).

Backup in Azure App Service

What Does a Backup Include?

Web App Content

Includes files, settings, and directories inside your App Service (like code, configurations, and other files).

App Settings & Configuration

Includes environment settings, connection strings, and app configuration data.

Databases (optional)

If your app uses an Azure SQL Database or other database resources, you can choose to back up the databases as well.

However, this is not automatic and must be handled separately (e.g., via Azure SQL Database backups).

Where Are the Backups Stored?

Backups are stored in Azure Storage in a blobs container.

You can choose to store backups in a separate Azure Storage account or the default account linked with your App Service plan.

Backup Frequency & Retention

Scheduled Backups

You can configure automatic, scheduled backups at daily, weekly, or custom intervals.

Retention Period

You can set a retention period for backups (e.g., 30 days, 60 days).

Older backups are automatically deleted once the retention period expires.

Manual Backups

In addition to automated backups, you can create manual backups whenever needed via the Azure portal.

How to Set Up Backup for an App Service

Step 1: Enable Backup for the App Service

1. Go to the Azure Portal:

   • Navigate to the App Service you want to back up.

2. Navigate to Backup Settings:

   • Under the Settings section, click "Backup".

3. Choose Backup Storage:

   • Select an Azure Storage Account to store your backups (or let Azure create one for you).

   • You can either use a default storage account or choose your own.

4. Set Backup Schedule:

   • Configure the frequency of backups (e.g., daily, weekly) and set the retention period.

   • If you want a manual backup, click "Backup Now".

5. Configure Databases (Optional):

   • If your app uses a database like Azure SQL Database, you can choose to back up your database as part of the backup process.

   • You’ll need to provide connection strings and credentials.

6. Save the Backup Settings:

   • Click "Save" to enable the backup process and schedule the first backup.

How to Manually Trigger a Backup

• Go to the App Service in the Azure Portal.

• In the Backup settings, click "Backup Now" to manually create a backup of the app.

This is useful when you make significant changes to the app or before deploying new code, so you can restore the app to the previous state if needed.

How to Restore an App Service from Backup

If something goes wrong with your app (e.g., incorrect changes, configuration errors, or a broken deployment), you can easily restore it from a backup.

Step 1: Go to the Backup Section

1. In the Azure Portal, navigate to the App Service that you want to restore.

2. Under the Settings section, select "Backup".

Step 2: Restore from Backup

1. Click on the "Restore" button.

2. Choose the backup you want to restore from the list of available backups.

3. You can select a specific point in time to restore your app, or choose the most recent backup.

Restore Options:

You can restore to the same app or to a different app (useful if you want to test the restored version before deploying it live).

Step 3: Confirm Restoration

Confirm the restore process.

The restore process will overwrite the current content, app settings, and configuration with the data from the backup.

1. Click "Restore" to begin the process.

Things to Know About Backup and Restore in Azure App Service

Backup Storage Costs

Storing backups in Azure Storage will incur costs based on the amount of data stored and the storage tier you choose.

The Standard tier provides a balance of performance and cost, while the Premium tier offers higher durability and performance.

Backup Limitations

App Service backups do not capture databases by default unless configured separately (e.g., Azure SQL Database backups).

If your app is using Azure App Service Environments (ASEs), additional considerations or configuration changes may be needed for backup and restore.

Backup Frequency

The minimum backup frequency for App Service backups is once a day.

However, for mission-critical apps, consider supplementing backups with manual backups or other disaster recovery strategies (like database-level backups).

Automatic Database Backups

For SQL databases, App Service backups do not include automatic backups of the database.

For databases, you will need to set up automatic backups for Azure SQL Database, Cosmos DB, or other databases as part of your overall backup strategy.

Backup Retention

App Service allows you to retain backups for a configurable period (e.g., 30 days, 60 days).

Be sure to monitor retention settings so that backups are deleted after the retention period, which is important for cost management.

App Configuration Settings

When restoring from a backup, it will overwrite the application’s configuration settings (including Application Settings, Connection Strings, and App Configuration), so ensure that no critical settings are lost.

Backup of Dependencies

Keep in mind that external dependencies (e.g., external APIs, Azure Blob Storage, or third-party services) are not included in the backup.

These dependencies need to be backed up or managed separately.

Backup Consistency

App Service backups aim to be consistent at the time of backup, but consider additional strategies for applications with complex dependencies, especially those that rely on databases or external services.

Restore Impact

Restoring from a backup may cause downtime, as the app will be replaced with the backup version.

You may want to test the restore process in a staging environment first to ensure everything functions as expected.

Best Practices for Backup and Restore

1. Regular Backups: Set up scheduled backups to run at regular intervals to minimize the risk of data loss.

2. Manual Backups Before Deployments: Always trigger a manual backup before making significant changes to the app (e.g., deploying new code).

3. Database Backups: Ensure your databases (e.g., Azure SQL, Cosmos DB) are backed up regularly using their respective backup features.

4. Test Your Backups: Periodically test your backup and restore process to ensure it works as expected in case of emergencies.

5. Monitor Retention: Ensure that backup retention policies are configured correctly to balance between storage costs and backup availability.

Summary

Backup and restore functionality in Azure App Service is crucial for protecting your web apps and their data.

By using the built-in backup tools, you can ensure that your app is recoverable in case of failure.

Remember to regularly back up, monitor backup configurations, and test your restore procedures to minimize risks and downtime.