Skip to content

Commit e8d9cf5

Browse files
minor changes
1 parent 742e5be commit e8d9cf5

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/backup/backup-azure-dataprotection-use-rest-api-restore-blobs.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article describes how to restore [blobs](blob-backup-overview.md) to any po
1818
1919
## Prerequisites
2020

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

2323
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`.
2424

@@ -194,7 +194,7 @@ The key points to remember in this scenario are:
194194

195195
## Validate restore requests
196196

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.
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.
198198

199199
```http
200200
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:
206206
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"
207207
```
208208

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.
210210

211211
### Response to validate restore requests
212212

213213
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.
214214

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.
216216

217217
|Name |Type |Description |
218218
|---------|---------|---------|
219219
|200 OK | | Status of validate request |
220220
|202 Accepted | | Accepted |
221221

222-
#### Example response to restore validate request
222+
#### Example response to restore validate-request
223223

224224
Once the *POST* operation is submitted, the initial response will be 202 Accepted along with an Azure-asyncOperation header.
225225

@@ -276,7 +276,7 @@ Once the requests are validated, the same request body can be used to trigger th
276276

277277
#### Example request body for all blobs restore
278278

279-
The only change from the validate restore request 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.
280280

281281
```json
282282
{
@@ -302,7 +302,7 @@ The only change from the validate restore request body is to remove the "restore
302302

303303
#### Example request body for items or few blobs restore
304304

305-
The only change from the validate restore request 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.
306306

307307
```json
308308
{
@@ -337,7 +337,7 @@ The only change from the validate restore request body is to remove the "restore
337337

338338
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.
339339

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.
341341

342342
|Name |Type |Description |
343343
|---------|---------|---------|

0 commit comments

Comments
 (0)