Skip to content

Commit c6ede08

Browse files
incorporate author feedback
1 parent 008c548 commit c6ede08

File tree

3 files changed

+6
-7
lines changed

3 files changed

+6
-7
lines changed

articles/backup/backup-azure-backup-sql.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,10 +87,9 @@ To protect SQL Server databases in Azure, first create a backup policy:
8787
> [!TIP]
8888
> For quick recovery, keep a few short-term recovery points on your disk. These recovery points are used for operational recovery. Azure serves as a good offsite location, providing higher SLAs and guaranteed availability.
8989
>
90+
> Use DPM to schedule Azure Backups after the local disk backups finish. When you follow this practice, the latest disk backup is copied to Azure.
9091
>
9192
92-
**Best practice**: Use DPM to schedule Azure Backups after the local disk backups finish. When you follow this practice, the latest disk backup is copied to Azure.
93-
9493
1. Choose the retention policy schedule. For more information about how the retention policy works, see [Use Azure Backup to replace your tape infrastructure](backup-azure-backup-cloud-as-tape.md).
9594

9695
![Choose a retention policy](./media/backup-azure-backup-sql/pg-retentionschedule.png)

articles/backup/backup-azure-sql-mabs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,9 +78,9 @@ To protect SQL Server databases in Azure, first create a backup policy:
7878
> [!TIP]
7979
> For quick recovery, keep a few short-term recovery points on your disk. These recovery points are used for operational recovery. Azure serves as a good offsite location, providing higher SLAs and guaranteed availability.
8080
>
81+
> Use Data Protection Manager (DPM) to schedule Azure Backups after the local disk backups finish. When you follow this practice, the latest disk backup is copied to Azure.
8182
>
8283
83-
**Best practice**: Use Data Protection Manager (DPM) to schedule Azure Backups after the local disk backups finish. When you follow this practice, the latest disk backup is copied to Azure.
8484

8585
1. Choose the retention policy schedule. For more information about how the retention policy works, see [Use Azure Backup to replace your tape infrastructure](backup-azure-backup-cloud-as-tape.md).
8686

articles/backup/backup-mabs-system-state-and-bmr.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -102,8 +102,6 @@ When the backup finishes, the file is transferred to the Backup Server computer.
102102

103103
## Back up system state and bare metal
104104

105-
Set up a protection group as described in [Deploy protection groups](https://docs.microsoft.com/system-center/dpm/create-dpm-protection-groups). Remember that you can't protect BMR and system state for the same computer in different groups. Also, when you select BMR, system state is automatically enabled.
106-
107105
To back up system state and bare metal:
108106

109107
1. To open the Create New Protection Group Wizard, in the Backup Server Administrator Console, select **Protection** > **Actions** > **Create Protection Group**.
@@ -181,7 +179,8 @@ To run recovery on the Backup Server computer:
181179
* You can create and split a clone to make it writable.
182180
* The protected computer and Backup Server computer are connected to the same network.
183181

184-
1. Set up notification options. On the **Confirmation** page, select **Recover**.
182+
1. Set up notification options.
183+
1. On the **Confirmation** page, select **Recover**.
185184

186185
To set up the share location:
187186

@@ -224,7 +223,8 @@ To run recovery in Backup Server:
224223
* You can create and split a clone to make it writable.
225224
* The protected computer and Backup Server server are connected to the same network.
226225

227-
1. Set up notification options. On the **Confirmation** page, select **Recover**.
226+
1. Set up notification options.
227+
1. On the **Confirmation** page, select **Recover**.
228228

229229
To run Windows Server Backup:
230230

0 commit comments

Comments
 (0)