Skip to content

Commit 345b464

Browse files
author
AbhishekMallick-MS
committed
Freshness - SQL DB backup
1 parent 689340c commit 345b464

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

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

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
title: Back up SQL Server to Azure as a DPM workload
33
description: An introduction to backing up SQL Server databases by using the Azure Backup service
44
ms.topic: how-to
5-
ms.date: 01/17/2023
5+
ms.date: 01/26/2024
66
ms.service: backup
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
9-
ms.custom: engagement-fy23
9+
ms.custom: engagement-fy24
1010
---
1111

1212
# 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
1515

1616
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/).
1717

18-
## SQL Server database backup workflow
18+
## Backup flow for SQL Server database
1919

2020
To back up a SQL Server database to Azure and to recover it from Azure:
2121

@@ -42,16 +42,16 @@ To back up a SQL Server database to Azure and to recover it from Azure:
4242
* DPM supports multi-site cluster configurations for an instance of SQL Server.
4343
* When you protect databases that use the Always On feature, DPM has the following limitations:
4444
* 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.
4646
* 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.
4747
* Primary - Backups should always occur on the primary replica.
4848
* 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.
5555
* SQL Server 2014 or above backup issues:
5656
* 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.
5757
* 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

Comments
 (0)