Recently, Microsoft announced the general availability of Backup of Azure IaaS VMs. The announcement is available here: http://azure.microsoft.com/en-us/blog/general-availability-of-backup-for-azure-iaas-vms/
This general availability means the backup mechanism of Azure virtual machines has changed. Before this general availability, Azure VMs were treated the same way as on-premises machine using an Agent that facilitates backup. While this method works great, the ‘new’ mechanism makes protection easier for Azure VMs.
To protect Azure VMs using an Azure Backup Vault, the following workflow can be used:
- Create a Backup Vault (if not used already)
- Register Azure VMs by discovering and select them for protection
- Setup a Backup Policy
- Start protecting
Keep in mind that each Backup Vault can store 54,4 TB of Backup content
This post describes the steps to configure Backup of Azure VMs.
- Create a Backup Vault
Pretty self-explanatory if you ask me.
- Register Azure VMs and Setup a backup policy
Once the Backup Vault has been created, Azure VMs can be registered for protection
Select the machines that need to be registered for protection and press the OK button. Press the protect button in the portal to proceed.
Press the Next button.
Here a protection policy can be configured. In this case a daily backup is scheduled at 8 pm.
The final step is defining the retention range. Notice that these settings are the same as in the Azure Recovery Services Agent. In this scenario a daily backup only is chosen. The configuration is completed after finishing the OK button
- Start protecting
An initial backup can be started by using the Backup Now button
Its progress can be monitored by the Jobs tab. This tab can also be used to view how long it takes for a machine to be backed up.
To restore a virtual machine, a new virtual machine can be created from ny backup set available…
This greatly simplifies protecting Azure VMs…