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
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
title: Back up SQL Server to Azure as a DPM workload
3
3
description: An introduction to backing up SQL Server databases by using the Azure Backup service
4
4
ms.topic: how-to
5
-
ms.date: 01/17/2023
5
+
ms.date: 01/26/2024
6
6
ms.service: backup
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-abhmallick
9
-
ms.custom: engagement-fy23
9
+
ms.custom: engagement-fy24
10
10
---
11
11
12
12
# Back up SQL Server to Azure as a DPM workload
@@ -15,7 +15,7 @@ This article describes how to back up and restore the SQL Server databases using
15
15
16
16
Azure Backup helps you to back up SQL Server databases to Azure via an Azure account. If you don't have one, you can create a free account in just a few minutes. For more information, see [Create your Azure free account](https://azure.microsoft.com/pricing/free-trial/).
17
17
18
-
## SQL Server database backup workflow
18
+
## Backup flow for SQL Server database
19
19
20
20
To back up a SQL Server database to Azure and to recover it from Azure:
21
21
@@ -42,16 +42,16 @@ To back up a SQL Server database to Azure and to recover it from Azure:
42
42
* DPM supports multi-site cluster configurations for an instance of SQL Server.
43
43
* When you protect databases that use the Always On feature, DPM has the following limitations:
44
44
* DPM will honor the backup policy for availability groups that's set in SQL Server based on the backup preferences, as follows:
45
-
* Prefer secondary - Backups should occur on a secondary replica except when the primary replica is the only replica online. If there are multiple secondary replicas available, then the node with the highest backup priority will be selected for backup. IF only the primary replica is available, then the backup should occur on the primary replica.
45
+
* Prefer secondary - Backups should occur on a secondary replica except when the primary replica is the only replica online. If there are multiple secondary replicas available, then the node with the highest backup priority will be selected for backup. If only the primary replica is available, then the backup should occur on the primary replica.
46
46
* Secondary only - Backup shouldn't be performed on the primary replica. If the primary replica is the only one online, the backup shouldn't occur.
47
47
* Primary - Backups should always occur on the primary replica.
48
48
* Any Replica - Backups can happen on any of the availability replicas in the availability group. The node to be backed up from will be based on the backup priorities for each of the nodes.
49
-
* Note the following:
50
-
* Backups can happen from any readable replica - that is, primary, synchronous secondary, asynchronous secondary.
51
-
* If any replica is excluded from backup, for example **Exclude Replica** is enabled or is marked as not readable, then that replica won't be selected for backup under any of the options.
52
-
* If multiple replicas are available and readable, then the node with the highest backup priority will be selected for backup.
53
-
* If the backup fails on the selected node, then the backup operation fails.
54
-
* Recovery to the original location isn't supported.
49
+
>[!Note]
50
+
>- Backups can happen from any readable replica - that is, primary, synchronous secondary, asynchronous secondary.
51
+
>- If any replica is excluded from backup, for example **Exclude Replica** is enabled or is marked as not readable, then that replica won't be selected for backup under any of the options.
52
+
>- If multiple replicas are available and readable, then the node with the highest backup priority will be selected for backup.
53
+
>- If the backup fails on the selected node, then the backup operation fails.
54
+
>- Recovery to the original location isn't supported.
55
55
* SQL Server 2014 or above backup issues:
56
56
* SQL server 2014 added a new feature to create a [database for on-premises SQL Server in Microsoft Azure Blob storage](/sql/relational-databases/databases/sql-server-data-files-in-microsoft-azure). DPM can't be used to protect this configuration.
57
57
* There are some known issues with "Prefer secondary" backup preference for the SQL Always On option. DPM always takes a backup from secondary. If no secondary can be found, then the backup fails.
0 commit comments