The backup operation includes the following stages:
- Discover virtual machine in the Azure cloud based on subclient settings.
- Create a client computer entry for each virtual machine discovered.
- Identify the virtual machines targeted for backup and the VSA proxies that can be used to perform backups. VSA proxies can be installed on Azure virtual machines or on local physical or virtual machines.
For Azure Classic backups, the VSA proxy must have an Azure management certificate installed.
- Identify the disks associated with virtual machines targeted for backup.
- Assign backup streams to proxies in round-robin sequence.
- Use the Virtual Server Agent (VSA) to communicate with Azure to download data.
- Create virtual machine snapshots in the Azure cloud. By default, Azure backups are crash consistent backups. There are two methods of backup :
- Cyclic Redundancy Check (CRC): Read extents from snapshots, compute CRC and write to backup media. After backup completes, delete the snapshots.
- Changed Block Tracking (CBT): With this option enabled by default at the subclient level, only the extents that have changed in between consecutive CBT-enabled jobs are backed up. This is completed with Azure API comparing the modified extents between the two consecutive jobs, reading these extents and then writing it to backup media. Once the backup is complete, upload the details of current snapshot to the index, delete the snapshots of the previous CBT-enabled job that was used for comparison and save the current job’s snapshots to be used in the next CBT incremental job for validation.
NOTE: Microsoft has a limitation on bandwidth for the snapshots created on unmanaged disks that reside in a premium storage account. As a workaround, a staging blob is created from the snapshot. Then, the backup operations read from the staging blob. After the backup job completes, the staging blob is deleted.
- Clean up the Azure mount point, and complete the backup job.
- If the virtual machine is encrypted using Azure Key Vault, the key information and secret information will be included in the backup as well. This is required at the time of restore in order to boot up the VM successfully by restoring the backed up encrypted files (secrets and keys).
Last modified: 9/10/2019 8:42:00 PM