Use the Azure portal to restore virtual machines
Protect your data by taking snapshots of your data at defined intervals. These snapshots are known as recovery points, and they're stored in Recovery Services vaults. If it's necessary to repair or rebuild a virtual machine (VM), you can restore the VM from any of the saved recovery points. When you restore a recovery point, you can:
- Create a new VM: From a point-in-time recovery point of your backed-up VM.
- Restore disks: Use the template that comes with the process to customize the restored VM, or do an individual file recovery.
This article explains how to restore a VM to a new VM or restore all backed-up disks. For individual file recovery, see Recover files from an Azure VM backup.
Restoring a VM or all disks from VM backup involves two steps:
- Select a restore point for restore.
- Select the restore type
- Option 1: Create a new VM
- Option 2: Restore disks.
Select a restore point for restore
Sign in to the Azure portal.
On the Azure menu, select All services. In the list of services, type Recovery Services or go to STORAGE where the Recovery Service vaults is listed, select it.
The list of vaults in the subscription is displayed.
From the list of Recovery Service vaults, select the vault associated with the VM you want to restore. When you select the vault, its dashboard opens.
In the vault dashboard, on the Backup Items tile, select Azure Virtual Machine.
The Backup Items blade with the list of Azure VMs is opened.
From the list, select a VM to open the dashboard. The VM dashboard opens to the monitoring area, which contains the Recovery points. All VM level operations like Backup now, File recovery, Stop backup can be performed from this blade. Restore can be performed in many ways from this blade. Note that this blade lists only the last 30 days recovery points.
- To restore using a restore point from the last 30 days, right-click the VM > Restore VM.
- To restore using a restore point older than 30 days, click the link under Restore Points.
- To list and filter VMs with customized dates, click Restore VM in the menu. Use the filter to modify the time range for the displayed restore points. You can also filter on different types of data consistency.
Review the restore point settings:
- Data consistency shows the type of consistency in the recovery point.
- The Recovery Type shows where the point is stored (in a storage account, in the vault, or both. Learn more about instant recovery points.
Select a restore point.
Select Restore configuration. The Restore configuration blade opens.
Choose a VM restore configuration
After you select the restore point, choose a VM restore configuration. To configure the restored VM, you can use the Azure portal or PowerShell.
|Create new-create VM||Equivalent to quick create of a VM. Gets a basic VM up and running from a restore point.
The VM settings can be modified as part of the restore process.
|Create new-restore disk||Creates a VM that you can customize as part of the restore process.
This option copies VHDs to the storage account you specify.
- The storage account should be in the same location as the vault.
If you don't have an appropriate storage account you need to create one.
The storage account replication type is shown in parentheses. Zone redundant storage (ZRS) isn't supported.
From the storage account you can either attach the restored disks to an existing VM, or create a new VM from the restored disks using PowerShell.
|Replace existing||With this option you don't need to create a VM.
The current VM must exist. If it's been deleted this option can't be used.
Azure Backup takes a snapshot of the existing VM and stores it in the staging location specified. The existing disks connected to the VM are then replaced with the selected restore point. The snapshot created previously is copied to the vault and stored as a recovery point in accordance with your backup retention policy.
Replace existing is supported for unencrypted managed VMs. It's not supported for unmanaged disks, generalized VMs, or for VMs created using custom images.
If the restore point has more or less disks than the current VM, then the number of disks in the restore point will only reflect the VM.
If you want to restore a VM with advanced networking settings, for example if they're managed by an internal or external load balancer, or have multiple NICs or multiple reserved IP addresses, restore with PowerShell. Learn more. If a Windows VM uses HUB licensing, use the Create new-restore disk option, and then use PowerShell or the restore template to create the VM with License Type set to Windows_Server. This setting can also be applied after creating the VM.
Specify the restore setting as follows:
- In Restore, select a restore point > Restore configuration.
In Restore configuration, select how you want to restore the VM in accordance with the settings summarized in the table above.
Create new-Create a VM
- In Restore configuration > Create new > Restore Type, select Create a virtual machine.
- In Virtual machine name, specify a VM which doesn’t exist in the subscription.
- In Resource group, select an existing resource group for the new VM, or create a new one with a globally unique name. If you assign a name that already existing, Azure assigns the group the same name as the VM.
- In Virtual network, select the VNet in which the VM will be placed. All VNets associated with the subscription are displayed. Select the subnet. The first subnet is selected by default.
In Storage Location, specify the storage type used for the VM.
In Restore configuration, select OK. In Restore, click Restore to trigger the restore operation.
Create new-Restore disks
- In Restore configuration > Create new > Restore Type, select Restore disks.
- In Resource group, select an existing resource group for the restored disks, or create a new one with a globally unique name.
In Storage account, specify the account to which to copy the VHDs. Make sure the account is in the same region as the vault.
In Restore configuration, select OK. In Restore, click Restore to trigger the restore operation.
After the disk is restored, you can do any of the following to complete the VM restore operation.
- Use the template that was generated as part of the restore operation to customize settings, and trigger VM deployment. You edit the default template settings, and submit the template for VM deployment.
- You can attach the restored disks to an existing VM.
- You can create a new VM from the restored disks using PowerShell.
Replace existing disks
Use this option to replace existing disks in the current VM with the selected restore point.
- In Restore configuration, click Replace existing.
- In Restore Type, select Replace disk/s (the restore point that will replace the existing VM disk or disks).
In Staging Location, specify where snapshots of the current managed disks should be saved.
Track the restore operation
After you trigger the restore operation, the backup service creates a job for tracking the restore operation. The backup service also creates and temporarily displays the notification in the Notifications area of the portal. If you don't see the notification, select the Notifications symbol to view your notifications.
Click on the hyperlink of the notifications to go to BackupJobs list. All the details of the operations for a given job is available in the BackupJobs lists. You can go to BackupJobs from the vault dashboard by clicking the Backup Jobs tile, select Azure virtual machine to display the jobs associated with the vault.
The Backup jobs blade opens and displays the list of jobs.
Progress bar is now available in the Restore Details blade. The Restore Details blade can be opened by clicking any restore job which has status in-progress. The Progress bar is available in all variants of restores like Create New, Restore Disk and Replace existing. The details carried by Restore Progress bar are estimated time of restore, percentage of restore and number of bytes transferred.
Restore Progress bar details are given below:
- Estimated time of restore initially provides the time taken to complete the restore operation. As the operation progresses, the time taken reduces and reaches 0 once the restore operation completes.
- Percentage of restore provides the data how much percentage of restore operation is completed.
- Number of bytes transferred is available in the sub task when restore happens through Create New VM. This provides the details of how many numbers of bytes were transferred against the total number of bytes to be transferred.
Use templates to customize a restored VM
After the restore disks operation is finished, use the template that was generated as part of the restore operation to create a new VM with a configuration different from the backup configuration. You also can use it to customize names of resources that were created during the process of creating a new VM from a restore point.
To get the template that was generated as part of the restore disks option:
Go to the Restore Job Details corresponding to the job.
On the Restore Job Details screen, select Deploy Template to initiate template deployment.
After you enter the required values, accept the Terms and Conditions and select Purchase.
- If you use a cloud-init-based Linux distribution, such as Ubuntu, for security reasons, the password is blocked post restore. Use the VMAccess extension on the restored VM to reset the password. We recommend using SSH keys on these distributions to avoid resetting the password post restore.
- Extensions present during the backup configuration are installed, but they won't be enabled. If you see an issue, reinstall the extensions.
- If the backed-up VM has static IP post restore, the restored VM has a dynamic IP to avoid conflict when you create a restored VM. Learn more about how you can add a static IP to a restored VM.
- A restored VM doesn't have an availability value set. We recommend using the restore disks option to add an availability set when you create a VM from PowerShell or templates by using restored disks.
Backup for restored VMs
If you restored a VM to the same resource group with the same name as the originally backed-up VM, backup continues on the VM post restore. If you restored the VM to a different resource group or you specified a different name for the restored VM, the VM is treated as if it's a new VM. You need to set up backup for the restored VM.
Restore a VM during an Azure datacenter disaster
Azure Backup allows restoring backed-up VMs to the paired datacenter in case the primary datacenter where VMs are running experiences a disaster and you configured the backup vault to be geo-redundant. During such scenarios, select a storage account, which is present in a paired datacenter. The rest of the restore process remains the same. Backup uses the compute service from the paired geo to create the restored VM. For more information, see Azure datacenter resiliency.
Restore domain controller VMs
Backup of domain controller (DC) VMs is a supported scenario with Backup. However, you must be careful during the restore process. The correct restore process depends on the structure of the domain. In the simplest case, you have a single DC in a single domain. More commonly for production loads, you have a single domain with multiple DCs, perhaps with some DCs on-premises. Finally, you might have a forest with multiple domains.
From an Active Directory perspective, the Azure VM is like any other VM on a modern supported hypervisor. The major difference with on-premises hypervisors is that there's no VM console available in Azure. A console is required for certain scenarios, such as recovering by using a bare-metal recovery (BMR)-type backup. However, VM restore from the backup vault is a full replacement for BMR. Directory Services Restore Mode (DSRM) is also available, so all Active Directory recovery scenarios are viable. For more information, see Backup and restore considerations for virtualized domain controllers and Planning for Active Directory forest recovery.
Single DC in a single domain
The VM can be restored (like any other VM) from the Azure portal or by using PowerShell.
Multiple DCs in a single domain
When other DCs of the same domain can be reached over the network, the DC can be restored like any VM. If it's the last remaining DC in the domain, or a recovery in an isolated network is performed, a forest recovery procedure must be followed.
Multiple domains in one forest
When other DCs of the same domain can be reached over the network, the DC can be restored like any VM. In all other cases, we recommend a forest recovery.
Restore VMs with special network configurations
It's possible to back up and restore VMs with the following special network configurations. However, these configurations require some special consideration while going through the restore process:
- VMs under load balancers (internal and external)
- VMs with multiple reserved IPs
- VMs with multiple NICs
When you create the special network configuration for VMs, you must use PowerShell to create VMs from the restored disks.
To fully re-create the VMs after restoring to disk, follow these steps:
Restore the disks from a Recovery Services vault by using PowerShell.
Create the VM configuration required for load balancer/multiple NIC/multiple reserved IP by using the PowerShell cmdlets. Use it to create the VM with the configuration you want:
a. Create a VM in the cloud service with an internal load balancer.
b. Create a VM to connect to an internet-facing load balancer.
c. Create a VM with multiple NICs.
d. Create a VM with multiple reserved IPs.
Now that you can restore your VMs, see the troubleshooting article for information on common errors with VMs. Also, check out the article on managing tasks with your VMs.