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-dataprotection-use-rest-api-restore-blobs.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ This article describes how to restore [blobs](blob-backup-overview.md) to any po
18
18
19
19
## Prerequisites
20
20
21
-
This article assumes that you have an operationalblobbackup configured for one or more of your storage accounts. [Learn how to configure a backup for block blob data](backup-azure-dataprotection-use-rest-api-backup-blobs.md), if not done.
21
+
This article assumes that you have an operational-blob-backup configured for one or more of your storage accounts. [Learn how to configure a backup for block blob data](backup-azure-dataprotection-use-rest-api-backup-blobs.md), if not done.
22
22
23
23
To illustrate the restoration steps in this article, we will refer to blobs in a storage account named `"msblobbackup-f2df34eb-5628-4570-87b2-0331d797c67d"` protected with an existing Backup vault `TestBkpVault`, under the resource group `testBkpVaultRG`.
24
24
@@ -194,7 +194,7 @@ The key points to remember in this scenario are:
194
194
195
195
## Validate restore requests
196
196
197
-
Once request body is prepared, it can be validated using the [validate for restore API](/rest/api/dataprotection/backup-instances/validate-for-restore). Like the validate forbackup API, this is a *POST* operation.
197
+
Once request body is prepared, it can be validated using the [validate for restore API](/rest/api/dataprotection/backup-instances/validate-for-restore). Like the Validate-for-backup API, this is a *POST* operation.
198
198
199
199
```http
200
200
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataProtection/backupVaults/{vaultName}/backupInstances/{backupInstanceName}/validateRestore?api-version=2021-01-01
@@ -206,20 +206,20 @@ For our example, this translates to:
206
206
POST "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx/resourceGroups/TestBkpVaultRG/providers/Microsoft.DataProtection/backupVaults/testBkpVault/backupInstances/msblobbackup-f2df34eb-5628-4570-87b2-0331d797c67d/validateRestore?api-version=2021-01-01"
207
207
```
208
208
209
-
The request body for this POST API is detailed [here](/rest/api/dataprotection/backup-instances/validate-for-restore#request-body). We have constructed the same in the above section for [all blobs restore](#constructing-the-request-body-for-point-in-time-restore-of-all-blobs) and [few items restore](#constructing-the-request-body-for-point-in-time-restore-of-selected-containers-or-few-blobs) scenarios. We will use the same to trigger a validate operation.
209
+
The request body for this POST API is detailed [here](/rest/api/dataprotection/backup-instances/validate-for-restore#request-body). We have constructed the same in the above section for [all blobs restore](#construct-the-request-body-for-point-in-time-restore-of-all-blobs) and [few items restore](#constructing-the-request-body-for-point-in-time-restore-of-selected-containers-or-few-blobs) scenarios. We will use the same to trigger a validate operation.
210
210
211
211
### Response to validate restore requests
212
212
213
213
The validate restore request is an [asynchronous operation](../azure-resource-manager/management/async-operations.md). It means this operation creates another operation that needs to be tracked separately.
214
214
215
-
It returns two responses: 202 (Accepted) when another operation is created and then 200 (OK) when that operation completes.
215
+
It returns two responses: 202 (Accepted) when another operation is created, and 200 (OK) when that operation completes.
216
216
217
217
|Name |Type |Description |
218
218
|---------|---------|---------|
219
219
|200 OK || Status of validate request |
220
220
|202 Accepted || Accepted |
221
221
222
-
#### Example response to restore validaterequest
222
+
#### Example response to restore validate-request
223
223
224
224
Once the *POST* operation is submitted, the initial response will be 202 Accepted along with an Azure-asyncOperation header.
225
225
@@ -276,7 +276,7 @@ Once the requests are validated, the same request body can be used to trigger th
276
276
277
277
#### Example request body for all blobs restore
278
278
279
-
The only change from the validaterestorerequest body is to remove the "restoreRequest" object at the start.
279
+
The only change from the validate-restore-request body is to remove the "restoreRequest" object at the start.
280
280
281
281
```json
282
282
{
@@ -302,7 +302,7 @@ The only change from the validate restore request body is to remove the "restore
302
302
303
303
#### Example request body for items or few blobs restore
304
304
305
-
The only change from the validaterestorerequest body is to remove the "restoreRequest" object at the start.
305
+
The only change from the validate-restore-request body is to remove the "restoreRequest" object at the start.
306
306
307
307
```json
308
308
{
@@ -337,7 +337,7 @@ The only change from the validate restore request body is to remove the "restore
337
337
338
338
The trigger restore request is an [asynchronous operation](../azure-resource-manager/management/async-operations.md). It means this operation creates another operation that needs to be tracked separately.
339
339
340
-
It returns two responses: 202 (Accepted) when another operation is created and then 200 (OK) when that operation completes.
340
+
It returns two responses: 202 (Accepted) when another operation is created, and 200 (OK) when that operation completes.
0 commit comments