Questions about the Azure VM Backup service
This article has answers to common questions to help you quickly understand the Azure VM Backup components. In some of the answers, there are links to the articles that have comprehensive information. You can also post questions about the Azure Backup service in the discussion forum.
Do Recovery Services vaults support classic VMs or Resource Manager based VMs?
Recovery Services vaults support both models. You can back up a classic VM (created in the Classic portal), or a Resource Manager VM (created in the Azure portal) to a Recovery Services vault.
What configurations are not supported by Azure VM backup?
Why can't I see my VM in configure backup wizard?
In Configure backup wizard, Azure Backup only lists VMs that are:
- Not already protected You can verify the backup status of a VM by going to VM blade and checking Backup status from Settings Menu . Learn more on how to Check backup status of a VM
- Belongs to same region as VM
Will on-demand backup job follow same retention schedule as scheduled backups?
No. You should specify the retention range for an on-demand backup job. By default, it is retained for 30 days when triggered from portal.
I recently enabled Azure Disk Encryption on some VMs. Will my backups continue to work?
You need to give permissions for Azure Backup service to access Key Vault. You can provide these permissions in PowerShell using steps mentioned in Enable Backup section of PowerShell documentation.
I migrated disks of a VM to managed disks. Will my backups continue to work?
Yes, backups work seamlessly and no need to reconfigure backup.
My VM is shut down. Will an on-demand or a scheduled backup work?
Yes. Even when a machine is shut down backups work and the recovery point is marked as Crash consistent. For more details, see the data consistency section in this article
Can I cancel an in-progress backup job?
Yes. You can cancel backup job if it is in "Taking snapshot" phase. You can't cancel a job if data transfer from snapshot is in progress.
I enabled Resource Group lock on my backed-up managed disk VMs. Will my backups continue to work?
If the user locks the Resource Group, Backup service is not able to delete the older restore points. Due to this new backups start failing as there is a limit of maximum 18 restore points imposed from the backend. If your backups are failing with an internal error after the RG lock, follow these steps to remove the restore point collection.
How do I decide between restoring disks versus full VM restore?
Think of Azure full VM restore as a quick create option. Restore VM option changes the names of disks, containers used by those disks, public IP addresses and network interface names. The change is required to maintain the uniqueness of resources created during VM creation. But it will not add the VM to availability set.
Use restore disks to:
- Customize the VM that gets created from point in time configuration like changing the size
- Add configurations, which are not present at the time of backup
- Control the naming convention for resources getting created
- Add VM to availability set
- For any other configuration which can be achieved only by using PowerShell/a declarative template definition
Can I use backups of unmanaged disk VM to restore after I upgrade my disks to managed disks?
Yes, you can use the backups taken before migrating disks from unmanaged to managed. By default, restore VM job will create a VM with unmanaged disks. You can use restore disks functionality to restore disks and use them to create a VM on managed disks.
What is the procedure to restore a VM to a restore point taken before the conversion from unmanaged to managed disks was done for a VM?
In this scenario, by default, restore VM job will create a VM with unmanaged disks. To create a VM with managed disks:
- Restore to unmanaged disks
- Convert the restored disks to managed disks
- Create a VM with managed disks
For Powershell cmdlets, refer here.
Manage VM backups
What happens when I change a backup policy on VM(s)?
When a new policy is applied on VM(s), schedule and retention of the new policy is followed. If retention is extended, existing recovery points are marked to keep them as per new policy. If retention is reduced, they are marked for pruning in the next cleanup job and subsequently deleted.
How can I move a VM enrolled in Azure backup between resource groups?
Follow the below steps to successfully move the backed-up VM to the target resource group
- Temporarily stop backup and retain backup data
- Move the VM to the target resource group
- Re-protect it with same/new vault
Users can restore from the available restore points created before the move operation.