Edit

Share via

Overview of VM restore points

  • Article

Business continuity and disaster recovery solutions are primarily designed to address sitewide data loss. Solutions that operate at this scale often manage and run across automated failovers and failbacks in multiple regions. You can use Azure virtual machine (VM) restore points to implement granular backup and retention policies.

You can protect your data and guard against extended downtime by creating VM restore points at regular intervals. There are several backup options available for VMs, depending on your use case. For more information, see Backup and restore options for VMs in Azure.

About VM restore points

An individual VM restore point is a resource that stores VM configuration and point-in-time application-consistent snapshots of all the managed disks attached to the VM. You can use VM restore points to easily capture multidisk-consistent backups. VM restore points contain a disk restore point for each of the attached disks. A disk restore point consists of a snapshot of an individual managed disk.

VM restore points support both application consistency and crash consistency.

Application consistency is supported for VMs running Windows operating systems and support file system consistency for VMs running Linux operating systems. Application-consistent restore points use Volume Shadow Copy Service (VSS) writers (or pre- and postscripts for Linux) to ensure the consistency of the application data before a restore point is created. To get an application-consistent restore point, the application running in the VM needs to provide a VSS writer (for Windows) or pre- and postscripts (for Linux) to achieve application consistency.

A multidisk crash-consistent VM restore point stores the VM configuration and point-in-time write-order-consistent snapshots for all managed disks attached to a VM. This information is the same as the status of data in the VM after a power outage or a crash. The consistencyMode optional parameter has to be set to crashConsistent in the creation request.

Note

For disks configured with read/write host caching, multidisk crash consistency can't be guaranteed because writes that occur while the snapshot is taken might not be acknowledged by Azure Storage. If maintaining consistency is crucial, we recommend that you use the application-consistency mode.

VM restore points are organized into restore point collections. A restore point collection is an Azure Resource Manager resource that contains the restore points for a specific VM. If you want to utilize Azure Resource Manager templates (ARM templates) for creating restore points and restore point collections, see the public Virtual-Machine-Restore-Points repository in GitHub.

The following image illustrates the relationship between restore point collections, VM restore points, and disk restore points.

A diagram that shows the relationship between the restore point collection parent and the restore point child objects.

VM restore points are incremental. The first restore point stores a full copy of all disks attached to the VM. For each successive restore point for a VM, only the incremental changes to your disks are backed up. To reduce your costs, you can optionally exclude any disk when you create a restore point for your VM.

Restore points for VMs inside virtual machine scale set and availability set (AvSet)

Currently, you can create restore points in only one VM at a time. You can't create a single restore point across multiple VMs. Because of this limitation, we currently support creating restore points for individual VMs with a virtual machine scale set in Flexible Orchestration mode or an availability set. If you want to back up instances within a virtual machine scale set instance or your availability set instance, you must individually create restore points for all the VMs that are part of the instance.

Note

A virtual machine scale set with Uniform orchestration isn't supported by restore points. You can't create restore points of VMs inside a virtual machine scale set with Uniform orchestration.

Throttling limits for Restore points

Scope Operation Limit per hour
VM RestorePoints.RestorePointOperation.PUT (Create new Application Consistent) 3
VM RestorePoints.RestorePointOperation.PUT (Create new Crash Consistent) 3
Target restore point collection RestorePoints.RestorePointOperation.PUT (Copy any VM Restore Point) 3

The throttling would fail with error code 429. Please retry the operation after the specified duration.

Limitations

  • Restore points are supported only for managed disks.
  • Ultra disks, Premium SSD v2 disks, Write-accelerated disks, Ephemeral OS disks, and shared disks aren't supported for crash consistency mode.
  • Ephemeral OS disks, and shared disks aren't supported for application consistency mode.
  • The API version for an application-consistent restore point is 2021-03-01, or later.
  • The API version for a crash-consistent restore point is 2021-07-01, or later.
  • Crash consistent restore point is supported on all Azure public regions.
  • Crash consistent restore point is supported for VM sizes that support Premium storage like DSv2.
  • A maximum of 500 VM restore points can be retained at any time for a VM, irrespective of the number of restore point collections or consistency type.
  • Concurrent creation of restore points for a VM isn't supported.
  • Restore points for virtual machine scale sets in Uniform orchestration mode aren't supported.
  • Movement of VMs between resource groups or subscriptions isn't supported when the VM has restore points. Moving the VM between resource groups or subscriptions doesn't update the source VM reference in the restore point and causes a mismatch of Resource Manager IDs between the actual VM and the restore points.

Note

Public preview of cross-region copying of VM restore points is available, with the following limitations:

  • Private links aren't supported when you copy restore points across regions or create restore points in a region other than the source VM.
  • Customer-managed key encrypted restore points, when copied to a target region, are created as platform-managed key encrypted restore points.

Troubleshoot VM restore points

Most common restore point failures are attributed to the communication with the VM agent and extension. To resolve failures, follow the steps in Troubleshoot restore point failures.

Next steps