Azure App Service Backup

Backup & restore vs. disaster recovery

Automatic vs. custom backups

Restore a backup

Restoring a backup in Azure can vary depending on the specific resource or service you are dealing with. Here is a general overview of how to restore a backup in Azure:

• Identify the Resource: Determine the Azure resource you want to restore, such as a virtual machine, database, storage account, etc.

• Access the Backup:

  • Azure Virtual Machines: If you want to restore a virtual machine, you can use Azure Backup. In the Azure portal, navigate to the specific virtual machine, click on "Backup," and then select the recovery point you want to restore.
  • Azure SQL Database: For SQL databases, you can use Azure SQL Database's built-in point-in-time restore feature. In the Azure portal, go to the SQL database you want to restore, click on "Restore," and select a restore point.
  • Azure Blob Storage: If you're dealing with data stored in Azure Blob Storage, you can access and restore your data using tools like Azure Storage Explorer or Azure PowerShell.

• Initiate Restore:

  • Follow the prompts and options provided by the Azure service you are using to initiate the restore process.
  • Configure settings such as the target location, resource name, and other parameters as required.

• Verify Restored Resource: After the restore is completed, it's essential to verify the restored resource's functionality to ensure that it's working correctly.

Create a custom backup

Creating a custom backup in Azure typically involves using Azure's backup and recovery services or specific tools designed for the resource you want to back up. Here are some general steps to create a custom backup:

• Configure Backup Settings: Define backup schedules, retention policies, and other backup settings as needed. This includes specifying how often backups should occur, how long they should be retained, and any encryption or access control requirements.
• Initiate the Backup: Depending on the Azure service, you may need to initiate the backup manually, or it may run automatically according to the configured schedule.

Configure custom scheduled backups

Configure Custom Scheduled Backups for an Azure Virtual Machine:

• Create or Select a Recovery Services Vault: If you don't have one, create a Recovery Services Vault in the Azure portal. This vault is used to store backup data.
• Install Azure Backup Agent (Windows VM): If you're backing up a Windows VM, you'll need to install the Azure Backup Agent on the virtual machine. You can download it from the Azure portal.
• Enable Backup: In the Azure portal, navigate to the virtual machine you want to back up. Under the "Operations" section, click on "Backup" to configure backup settings.
• Configure Backup Policy: Create a custom backup policy by selecting the desired settings for backup frequency, retention, and time zone. You can also set up daily, weekly, or monthly backups.
• Specify Items to Back Up: Choose what you want to back up on the virtual machine, such as files, folders, or system state.
• Review and Save: Review the settings to ensure they match your requirements, and then save the configuration.
• Schedule the Backup: Define the start time for your scheduled backups. You can choose to run the backups immediately or at a specific time.
• Review and Save: Double-check your settings, and then save the backup configuration.

Backup and restore over Azure Virtual Network (preview)

specific to Azure App Service environments (including v3 App Service environments) and allows you to configure custom backups for app files and configuration data while ensuring the data transfer occurs over the Azure Virtual Network for added security and compliance.

• Access Backup Settings: Access the backup settings for your Azure App Service environment.

• Configure Backup:

  • While configuring custom backups, look for the option to enable "Backup/restore over virtual network integration."
  • Save your settings by selecting the "Configure" option.

• Validation: If you don't see the checkbox or it's disabled, verify that all the prerequisites mentioned in the first step are fulfilled.

• Backup and Restore Operations: Once the configuration is saved, any manual, scheduled backup, or restore operations are performed through the virtual network for enhanced security.

Configure partial backups

Partial backups are particularly useful when you want to exclude certain portions of your app from the backup process for various reasons, such as conserving storage, excluding non-essential data, or optimizing backup operations. Here's how to configure partial backups for your Azure App Service:

• Access Backup Settings: In the Azure portal, navigate to your Azure App Service that you want to configure partial backups for.
• Configure Custom Backups: While configuring custom backups for your app, you should have the option to select specific components or content to include or exclude from the backup.

How backups are stored

Backups in Azure are typically stored in Azure Storage, and the exact storage mechanism can vary depending on the Azure service and the specific backup solution you're using.

• Each backup for your app is stored in a .zip file format that contains the actual backup data.
• In addition to the .zip file, there is an associated .xml file that contains a manifest of the .zip file's contents. This manifest provides information about what is included in the backup.
• You have the option to access and view these backup files within your Azure Storage account. You can unzip the .zip file and browse its contents to inspect the backup data.
• If your app includes a database, the database backup is stored within the .zip file. For SQL Database, the database backup is in the form of a BACPAC file, which doesn't have a file extension. You can import this BACPAC file to create a database in Azure SQL Database.

Error messages

Azure Backup can encounter various errors during backup and restore operations. Below are some common errors that you might encounter and their potential causes and solutions:

• Error: "The backup operation failed because the file system metadata is corrupted."

  • Cause: Indicates corruption in the file system metadata.
  • Solution: Run a file system check (chkdsk for Windows, fsck for Linux) to repair file system issues.

• Error: "Backup failed due to insufficient space in the storage account."

  • Cause: The storage account has insufficient space to accommodate the backup.
  • Solution: Increase the capacity or adjust your backup retention settings to manage storage consumption.

• Error: "Authentication failed for Azure Backup."

  • Cause: Authentication issues with Azure Backup.
  • Solution: Verify credentials and access rights for Azure Backup service. Ensure that Multi-Factor Authentication (MFA) is properly configured if it's enabled.

• Error: "Backup failed because the selected file or folder doesn't exist."

  • Cause: The selected file or folder for backup doesn't exist.
  • Solution: Ensure the file or folder exists, or update your backup settings to reflect the correct location.

Automate with scripts

Automating tasks in Azure using scripts is a powerful way to streamline management and maintenance of your resources. Azure provides several ways to automate tasks, and you can use different scripting languages and tools to interact with Azure resources.