Skip to content

Commit 10e8934

Browse files
author
AbhishekMallick-MS
committed
Link updates
1 parent 34224a8 commit 10e8934

File tree

2 files changed

+13
-12
lines changed

2 files changed

+13
-12
lines changed

articles/backup/backup-azure-arm-userestapi-backupazurevms.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Back up Azure VMs using REST API in Azure Backup
33
description: In this article, learn how to configure, initiate, and manage backup operations of Azure VM Backup using REST API.
44
ms.topic: how-to
5-
ms.date: 04/23/2024
5+
ms.date: 04/24/2024
66
ms.assetid: b80b3a41-87bf-49ca-8ef2-68e43c04c1a3
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
@@ -90,7 +90,7 @@ X-Powered-By: ASP.NET
9090

9191
### Selecting the relevant Azure VM
9292

93-
You can confirm that "caching" is done by [listing all protectable items](/rest/api/backup/backup-protectable-items/list) under the subscription and locate the desired VM in the response. [The response of this operation](#example-responses-to-get-operation) also gives you information on how Recovery Services identifies a VM. Once you're familiar with the pattern, you can skip this step and directly proceed to [enabling protection](#enabling-protection-for-the-azure-vm).
93+
You can confirm that "caching" is done by [listing all protectable items](/rest/api/backup/backup-protectable-items/list) under the subscription and locate the desired VM in the response. [The response of this operation](#responses-to-get-operation) also gives you information on how Recovery Services identifies a VM. Once you're familiar with the pattern, you can skip this step and directly proceed to [enabling protection](#enable-protection-for-the-azure-vm).
9494

9595
This operation is a *GET* operation.
9696

@@ -151,7 +151,7 @@ The response contains the list of all unprotected Azure VMs and each `{value}` c
151151

152152
- containerName = "iaasvmcontainer;"+`{name}`
153153
- protectedItemName = "vm;"+ `{name}`
154-
- `{virtualMachineId}` is used later in [the request body](#example-request-body)
154+
- `{virtualMachineId}` is used later in [the request body](#enable-protection-for-the-azure-vm)
155155

156156
In the example, the above values translate to:
157157

@@ -198,7 +198,7 @@ The following request body defines properties required to create a protected ite
198198
}
199199
```
200200

201-
The `{sourceResourceId}` is the `{virtualMachineId}` mentioned above from the [response of list protectable items](#example-responses-to-get-operation).
201+
The `{sourceResourceId}` is the `{virtualMachineId}` mentioned above from the [response of list protectable items](#responses-to-get-operation).
202202
Responses to create protected item operation
203203
@01011011
204204

@@ -281,7 +281,7 @@ This confirms that protection is enabled for the VM and the first backup will be
281281

282282
### Excluding disks in Azure VM backup
283283

284-
Azure Backup also provides a way to selectively back up a subset of disks in Azure VM. More details are provided [here](selective-disk-backup-restore.md). If you want to selectively back up few disks during enabling protection, the following code snippet should be the [request body during enabling protection](#example-request-body).
284+
Azure Backup also provides a way to selectively back up a subset of disks in Azure VM. More details are provided [here](selective-disk-backup-restore.md). If you want to selectively back up few disks during enabling protection, the following code snippet should be the [request body during enabling protection](#create-the-request-body-for-on-demand-backup).
285285

286286
```json
287287
{
@@ -421,7 +421,7 @@ Since the backup job is a long running operation, it needs to be tracked as expl
421421

422422
### Changing the policy of protection
423423

424-
To change the policy with which VM is protected, you can use the same format as [enabling protection](#enabling-protection-for-the-azure-vm). Just provide the new policy ID in [the request body](#example-request-body) and submit the request. For example: To change the policy of testVM from 'DefaultPolicy' to 'ProdPolicy', provide the 'ProdPolicy' ID in the request body.
424+
To change the policy with which VM is protected, you can use the same format as [enabling protection](#enable-protection-for-the-azure-vm)). Just provide the new policy ID in [the request body](#create-the-request-body) and submit the request. For example: To change the policy of testVM from 'DefaultPolicy' to 'ProdPolicy', provide the 'ProdPolicy' ID in the request body.
425425

426426
```json
427427
{
@@ -494,7 +494,7 @@ It returns two responses: 202 (Accepted) when another operation is created, and
494494

495495
Undoing the accidental deletion is similar to creating the backup item. After you undo the deletion, the item is retained but no future backups are triggered.
496496

497-
Undo deletion is a *PUT* operation which is very similar to [changing the policy](#changing-the-policy-of-protection) and/or [enabling the protection](#enabling-protection-for-the-azure-vm). Just provide the intent to undo the deletion with the variable *isRehydrate* in [the request body](#example-request-body) and submit the request. For example: To undo the deletion for testVM, the following request body should be used.
497+
Undo deletion is a *PUT* operation which is very similar to [changing the policy](#changing-the-policy-of-protection) and/or [enabling the protection](#enable-protection-for-the-azure-vm). Just provide the intent to undo the deletion with the variable *isRehydrate* in [the request body](#create-the-request-body) and submit the request. For example: To undo the deletion for testVM, the following request body should be used.
498498

499499
```http
500500
{

articles/backup/backup-azure-arm-userestapi-restoreazurevms.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
---
22
title: Restore Azure VMs using REST API
33
description: In this article, learn how to manage restore operations of Azure Virtual Machine Backup using REST API.
4-
ms.topic: conceptual
5-
ms.date: 08/26/2021
4+
ms.topic: how-to
5+
ms.service: backup
6+
ms.date: 04/24/2024
67
ms.assetid: b8487516-7ac5-4435-9680-674d9ecf5642
78
author: AbhishekMallick-MS
89
ms.author: v-abhmallick
@@ -22,7 +23,7 @@ The available recovery points of a backup item can be listed using the [list rec
2223
GET https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints?api-version=2019-05-13
2324
```
2425

25-
The `{containerName}` and `{protectedItemName}` are as constructed [here](backup-azure-arm-userestapi-backupazurevms.md#example-responses-to-get-operation). `{fabricName}` is "Azure".
26+
The `{containerName}` and `{protectedItemName}` are as constructed [here](backup-azure-arm-userestapi-backupazurevms.md#responses-to-get-operation). `{fabricName}` is "Azure".
2627

2728
The *GET* URI has all the required parameters. There's no need for an additional request body.
2829

@@ -127,7 +128,7 @@ Triggering restore operations is a *POST* request. To know more about the API, r
127128
POST https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints/{recoveryPointId}/restore?api-version=2019-05-13
128129
```
129130

130-
The `{containerName}` and `{protectedItemName}` are as constructed [here](backup-azure-arm-userestapi-backupazurevms.md#example-responses-to-get-operation). `{fabricName}` is "Azure" and the `{recoveryPointId}` is the `{name}` field of the recovery point mentioned [above](#example-response).
131+
The `{containerName}` and `{protectedItemName}` are as constructed [here](backup-azure-arm-userestapi-backupazurevms.md#responses-to-get-operation). `{fabricName}` is "Azure" and the `{recoveryPointId}` is the `{name}` field of the recovery point mentioned [above](#example-response).
131132

132133
Once the recovery point is obtained, we need to construct the request body for the relevant restore scenario. The following sections outline the request body for each scenario.
133134

@@ -349,7 +350,7 @@ GET https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{
349350
350351
```
351352

352-
The `{containerName}` and `{protectedItemName}` are as constructed [here](backup-azure-arm-userestapi-backupazurevms.md#example-responses-to-get-operation). `{fabricName}` is "Azure".
353+
The `{containerName}` and `{protectedItemName}` are as constructed [here](backup-azure-arm-userestapi-backupazurevms.md#responses-to-get-operation). `{fabricName}` is "Azure".
353354

354355
The *GET* URI has all the required parameters. An additional request body isn't required.
355356

0 commit comments

Comments
 (0)