Skip to content

Commit 0682017

Browse files
GA - MDCC
1 parent 46e8a46 commit 0682017

File tree

1 file changed

+15
-3
lines changed

1 file changed

+15
-3
lines changed

articles/virtual-machines/virtual-machines-create-restore-points.md

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ You can protect your data and guard against extended downtime by creating VM res
2020

2121
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.
2222

23-
VM restore points support both application consistency and crash consistency (in preview). Fill out this [form](https://forms.office.com/r/LjLBt6tJRL) if you want to try crash-consistent restore points in preview.
23+
VM restore points support both application consistency and crash consistency.
2424

2525
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.
2626

27-
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. This feature is currently in preview.
27+
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.
2828

2929
> [!NOTE]
3030
> 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.
@@ -44,12 +44,24 @@ Currently, you can create restore points in only one VM at a time. You can't cre
4444
> [!NOTE]
4545
> 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.
4646
47+
## Throttling limits for Restore points
48+
49+
**Scope** | **Operation** | **Limit**
50+
--- | --- | ---
51+
VM | RestorePoints.RestorePointOperation.PUT (Create new **Application Consistent**) | 3
52+
VM | RestorePoints.RestorePointOperation.PUT (Create new **Crash Consisten**t) | 3
53+
Target restore point collection | RestorePoints.RestorePointOperation.PUT (Copy any VM Restore Point) | 3
54+
55+
The throttling would fail with error code 429. Please retry the operation after the specified duration.
56+
4757
## Limitations
4858

4959
- Restore points are supported only for managed disks.
5060
- Ultra-disks, ephemeral OS disks, and shared disks aren't supported.
5161
- The API version for an application-consistent restore point is March 1, 2021, or later.
52-
- The API version for a crash-consistent restore point is July 1, 2021, or later (in preview).
62+
- The API version for a crash-consistent restore point is July 1, 2021, or later.
63+
- Crash consistent is supported only for Premium VM SKUs.
64+
- Crash consistent restore points are not supported via portal. We will enable this soon.
5365
- A maximum of 500 VM restore points can be retained at any time for a VM, irrespective of the number of restore point collections.
5466
- Concurrent creation of restore points for a VM isn't supported.
5567
- Restore points for virtual machine scale sets in Uniform orchestration mode aren't supported.

0 commit comments

Comments
 (0)