You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> After taking a snapshot of an Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it. See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
90
+
> After taking a snapshot of a Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it. See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
91
91
92
92
You can identify incremental snapshots from the same disk with the `SourceResourceId` and the `SourceUniqueId` properties of snapshots. `SourceResourceId` is the Azure Resource Manager resource ID of the parent disk. `SourceUniqueId` is the value inherited from the `UniqueId` property of the disk. If you delete a disk and then create a new disk with the same name, the value of the `UniqueId` property changes.
> After taking a snapshot of an Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it. See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
117
+
> After taking a snapshot of a Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it. See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
@@ -152,7 +152,7 @@ You can also use Azure Resource Manager templates to create an incremental snaps
152
152
}
153
153
```
154
154
> [!IMPORTANT]
155
-
> After taking a snapshot of an Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it. See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
155
+
> After taking a snapshot of a Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it. See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
When creating a disk from either an Premium SSD v2 or an Ultra Disk snapshot, you must wait for the background copy process to complete before you can attach it. Currently, you must use the Azure CLI to check the progress of the copy process.
243
+
When creating a disk from either a Premium SSD v2 or an Ultra Disk snapshot, you must wait for the background copy process to complete before you can attach it. Currently, you must use the Azure CLI to check the progress of the copy process.
244
244
245
245
The following script gives you the status of an individual disk's copy process. The value of `completionPercent` must be 100 before the disk can be attached.
Copy file name to clipboardExpand all lines: includes/virtual-machines-disks-incremental-snapshots-restrictions.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,11 @@
5
5
author: roygara
6
6
ms.service: virtual-machines
7
7
ms.topic: include
8
-
ms.date: 02/13/2023
8
+
ms.date: 02/17/2023
9
9
ms.author: rogarana
10
10
ms.custom: include file
11
11
---
12
12
13
-
- Not currently available for Premium SSD v2 managed disks.
14
13
- Incremental snapshots currently can't be moved between subscriptions.
15
14
- You can currently only generate SAS URIs of up to five snapshots of a particular snapshot family at any given time.
16
15
- You can't create an incremental snapshot for a particular disk outside of that disk's subscription.
@@ -26,6 +25,6 @@ Incremental snapshots of Premium SSD v2 and Ultra Disks have the following extra
26
25
- You must request and receive access to the preview from the following link: [https://aka.ms/UltraPremiumv2SnapshotPreview](https://aka.ms/UltraPremiumv2SnapshotPreview)
27
26
- Currently only available in Sweden Central and US West 3.
28
27
- Snapshots with a 512 logical sector size are stored as VHD, and can be used to create any disk type. Snapshots with a 4096 logical sector size are stored as VHDX and can only be used to create Ultra Disks, they can't be used to create other disk types. To determine which sector size your snapshot is, see [check sector size](#check-sector-size).
29
-
- When an incremental snapshot of either an Premium SSD v2 or an Ultra Disk is created, a background copy process for that disk is started. While a background copy is ongoing, you can have up to three total snapshots pending. The process must complete before any more snapshots of that disk can be created.
30
-
- Incremental snapshots of an Premium SSD v2 or an Ultra disk can't be used immediately after they're created. The background copy must complete before you can create a disk from the snapshot. See [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) for details.
31
-
- Disks created from an incremental snapshot of an Premium SSD v2 or an Ultra Disk can't be immediately attached to a VM once it's created. The background copy must complete before it can be attached. See [Check disk creation status](#check-disk-creation-status) for details.
28
+
- When an incremental snapshot of either a Premium SSD v2 or an Ultra Disk is created, a background copy process for that disk is started. While a background copy is ongoing, you can have up to three total snapshots pending. The process must complete before any more snapshots of that disk can be created.
29
+
- Incremental snapshots of a Premium SSD v2 or an Ultra disk can't be used immediately after they're created. The background copy must complete before you can create a disk from the snapshot. See [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) for details.
30
+
- Disks created from an incremental snapshot of a Premium SSD v2 or an Ultra Disk can't be immediately attached to a VM once it's created. The background copy must complete before it can be attached. See [Check disk creation status](#check-disk-creation-status) for details.
0 commit comments