This article was originally posted in the Microsoft Azure blog.
We are excited to announce In-Place restore of disks in IaaS VMs along with simplified restore improvements in Azure Backup. This feature helps roll back or fix corrupted virtual machines through in-place restore without the needs of spinning up a new VM. With the introduction of this feature, customers have multiple choices for IaaS VM restore like create new VM, Restore Disks and Replace disks.
Customers can exercise this new capability by choosing the Replace existing tab in the Restore Configuration blade. The prerequisite for replacing disks operation is an existence of source IaaS VM. This operation is comprised of the following steps:
- Azure Backup first takes the snapshot of the IaaS VM before replacing the disks as the replace operation modifies the production VM. The snapshots taken are stored in the Staging location provided by the user.
- On successful completion of step 1, the existing disks connected to the VM are replaced using the selected restore point.
- In parallel to the step 2, the snapshot created in step 1 is copied to the vault and retained as per the customer specified retention policy.
Replace existing option is currently supported for unencrypted managed VMs. It is not supported for generalized VMs and for VMs created using custom images. We are also looking forward to add a capability to replace Azure VMs when restoring.
Related links and additional content
- More details on In-Place Restore
- Learn more about Azure Restore
- Want more details? Check out Azure Backup documentation
- Need help? Reach out to Azure Backup forum for support
- Tell us how we can improve Azure Backup by contributing new ideas and voting up existing ones
- Follow us on Twitter @AzureBackup for the latest news and updates