Skip to content

Commit ba64748

Browse files
author
AbhishekMallick-MS
committed
minor changes
1 parent 1256a8a commit ba64748

File tree

2 files changed

+5
-17
lines changed

2 files changed

+5
-17
lines changed

articles/backup/restore-managed-disks-cli.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,9 @@ This article describes how to restore [Azure Managed Disks](../virtual-machines/
1515
> [!IMPORTANT]
1616
> Support for Azure Managed Disks backup and restore via CLI is in preview and available as an extension in Az 2.15.0 version and later. The extension is automatically installed when you run the **az dataprotection** commands. [Learn more](/cli/azure/azure-cli-extensions-overview) about extensions.
1717
18-
Currently, the Original-Location Recovery (OLR) option of restoring by replacing the existing source disk from where the backups were taken isn't supported. You can restore from a recovery point to create a new disk in the same resource group of the source disk or in any other resource group. It's known as Alternate-Location Recovery (ALR).
18+
Currently, the Original-Location Recovery (OLR) option of restoring by replacing the existing source disk from where the backups were taken isn't supported. You can restore from a recovery point to create a new disk in the same resource group of the source disk or in any other resource group, which is called Alternate-Location Recovery (ALR).
1919

20-
In this article, you'll learn how to:
21-
22-
- Restore to create a new disk
23-
24-
- Track the restore operation status
25-
26-
We'll refer to an existing Backup vault _TestBkpVault_, under the resource group _testBkpVaultRG_ in the examples.
20+
Here, let's use an existing Backup vault _TestBkpVault_, under the resource group _testBkpVaultRG_ in the examples.
2721

2822
## Restore to create a new disk
2923

@@ -177,7 +171,7 @@ az dataprotection recovery-point list --backup-instance-name diskrg-CLITestDisk-
177171
]
178172
```
179173

180-
For example, the below query returns the latest recovery point.
174+
For example, the following query returns the latest recovery point.
181175

182176
```azurecli-interactive
183177
az dataprotection recovery-point list --backup-instance-name diskrg-CLITestDisk-3df6ac08-9496-4839-8fb5-8b78e594f166 -g testBkpVaultRG --vault-name TestBkpVault --query "[0].id"

articles/backup/restore-postgresql-database-cli.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,9 @@ ms.author: v-abhmallick
1313

1414
This article explains how to restore [Azure PostgreSQL databases](../postgresql/overview.md#azure-database-for-postgresql---single-server) to an Azure PostgreSQL server backed-up by Azure Backup.
1515

16-
Being a PaaS database, the Original Location Recovery (OLR) option to restore by replacing the existing database (from where the backups were taken) isn't supported. You can restore from a recovery point to create a new database in the same Azure PostgreSQL server or in any other PostgreSQL server. This is called Alternate-Location Recovery (ALR) that helps to keep both - the source database and the restored (new) database.
16+
Being a PaaS database, the Original Location Recovery (OLR) option to restore by replacing the existing database (from where the backups were taken) isn't supported. You can restore from a recovery point to create a new database in the same Azure PostgreSQL server or in any other PostgreSQL server, which is called Alternate-Location Recovery (ALR) that helps to keep both - the source database and the restored (new) database.
1717

18-
In this article, you'll learn how to:
19-
20-
- Restore to create a new PostgreSQL database
21-
22-
- Track the restore operation status
23-
24-
We'll refer to an existing Backup vault _TestBkpVault_, under the resource group _testBkpVaultRG_ in the examples.
18+
Here, let's use an existing Backup vault _TestBkpVault_, under the resource group _testBkpVaultRG_ in the examples.
2519

2620
## Restore a backed-up PostgreSQL database
2721

0 commit comments

Comments
 (0)