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
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-arm-userestapi-restoreazurevms.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,7 +118,7 @@ The recovery point is identified with the `{name}` field in the given response.
118
118
119
119
## Trigger the restore operations for Azure VM
120
120
121
-
After selecting the [relevant restore point](#select-recovery-point), proceed to trigger the restore operation.
121
+
After selecting the [relevant restore point](#select-recovery-point-for-azure-vm-restore), proceed to trigger the restore operation.
122
122
123
123
***All restore operations on the backup item are performed with the same *POST* API. Only the request body changes with the restore scenarios.***
124
124
@@ -211,7 +211,7 @@ Since the restore job is a long running operation, it should be tracked as expla
211
211
212
212
### Restore disks
213
213
214
-
If there's a need to customize the creation of a VM from the backup data, restore the disks into a chosen storage account and create a VM from those disks according to their requirements. The storage account should be in the same region as the Recovery Services vault and shouldn't be zone redundant. The disks, as well as the configuration of the backed-up VM ("vmconfig.json"), is stored in the given storage account. As explained [here](#restore-operations), the relevant request body for restore disks is provided below.
214
+
If there's a need to customize the creation of a VM from the backup data, restore the disks into a chosen storage account and create a VM from those disks according to their requirements. The storage account should be in the same region as the Recovery Services vault and shouldn't be zone redundant. The disks, as well as the configuration of the backed-up VM ("vmconfig.json"), is stored in the given storage account. As explained [here](#trigger-the-restore-operations-for-azure-vm), the relevant request body for restore disks is provided below.
215
215
216
216
#### Create request body
217
217
@@ -247,7 +247,7 @@ The following request body defines properties required to trigger a disk restore
247
247
248
248
### Restore disks selectively
249
249
250
-
If you're [selectively backing up disks](backup-azure-arm-userestapi-backupazurevms.md#excluding-disks-in-azure-vm-backup), then the current backed-up disk list is provided in the [recovery point summary](#select-recovery-point) and [detailed response](/rest/api/backup/recovery-points/get). You can also selectively restore disks and more details are provided [here](selective-disk-backup-restore.md#selective-disk-restore). To selectively restore a disk among the list of backed up disks, find the LUN of the disk from the recovery point response and add the **restoreDiskLunList** property to the [request body above](#example-request) as shown below.
250
+
If you're [selectively backing up disks](backup-azure-arm-userestapi-backupazurevms.md#excluding-disks-in-azure-vm-backup), then the current backed-up disk list is provided in the [recovery point summary](#select-recovery-point-for-azure-vm-restore) and [detailed response](/rest/api/backup/recovery-points/get). You can also selectively restore disks and more details are provided [here](selective-disk-backup-restore.md#selective-disk-restore). To selectively restore a disk among the list of backed up disks, find the LUN of the disk from the recovery point response and add the **restoreDiskLunList** property to the [request body above](#example-request) as shown below.
251
251
252
252
```json
253
253
{
@@ -273,7 +273,7 @@ Once you track the response as explained [here](#responses), and the long runnin
273
273
274
274
### Replace disks in a backed-up virtual machine
275
275
276
-
While restore disks creates disks from the recovery point, replace disks replaces the current disks of the backed-up VM with the disks from the recovery point. As explained [here](#restore-operations), the relevant request body for replacing disks is provided below.
276
+
While restore disks create disks from the recovery point, replace disks replaces the current disks of the backed-up VM with the disks from the recovery point. As explained [here](#trigger-the-restore-operations-for-azure-vm), the relevant request body for replacing disks is provided below.
277
277
278
278
#### Create request body
279
279
@@ -314,7 +314,7 @@ The following request body defines properties required to trigger a disk restore
314
314
315
315
### Restore as another virtual machine
316
316
317
-
As explained [above](#restore-operations), the following request body defines properties required to trigger a virtual machine restore.
317
+
As explained [above](#trigger-the-restore-operations-for-azure-vm), the following request body defines properties required to trigger a virtual machine restore.
0 commit comments