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-backup-sql.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,10 +87,9 @@ To protect SQL Server databases in Azure, first create a backup policy:
87
87
> [!TIP]
88
88
> 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.
89
89
>
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.
90
91
>
91
92
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
-
94
93
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).
95
94
96
95

Copy file name to clipboardExpand all lines: articles/backup/backup-azure-sql-mabs.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,9 +78,9 @@ To protect SQL Server databases in Azure, first create a backup policy:
78
78
> [!TIP]
79
79
> 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.
80
80
>
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.
81
82
>
82
83
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.
84
84
85
85
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).
Copy file name to clipboardExpand all lines: articles/backup/backup-mabs-system-state-and-bmr.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,8 +102,6 @@ When the backup finishes, the file is transferred to the Backup Server computer.
102
102
103
103
## Back up system state and bare metal
104
104
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
-
107
105
To back up system state and bare metal:
108
106
109
107
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:
181
179
* You can create and split a clone to make it writable.
182
180
* The protected computer and Backup Server computer are connected to the same network.
183
181
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**.
185
184
186
185
To set up the share location:
187
186
@@ -224,7 +223,8 @@ To run recovery in Backup Server:
224
223
* You can create and split a clone to make it writable.
225
224
* The protected computer and Backup Server server are connected to the same network.
226
225
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**.
0 commit comments