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-sql-server-on-availability-groups.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
title: Back up SQL Server always on availability groups
3
3
description: In this article, learn how to back up SQL Server on availability groups.
4
-
ms.topic: conceptual
5
-
ms.date: 01/25/2024
4
+
ms.topic: how-to
5
+
ms.date: 09/11/2024
6
6
author: AbhishekMallick-MS
7
7
ms.author: v-abhmallick
8
8
---
@@ -23,7 +23,7 @@ The backup preference used by Azure Backup SQL AG supports full and differential
23
23
| Prefer Secondary | Primary replica | Secondary replicas are preferred, but backups can run on primary replica also. |
24
24
| None/Any | Primary replica | Any replica |
25
25
26
-
The workload backup extension gets installed on the node when it's registered with the Azure Backup service. When an AG database is configured for backup, the backup schedules are pushed to all the registered nodes of the AG. The schedules fire on all the AG nodes and the workload backup extensions on these nodes synchronize between themselves to decide which node will perform the backup. The node selection depends on the backup type and the backup preference as explained in section 1.
26
+
The workload backup extension is installed on the node when you register it with the Azure Backup service. When an AG database is configured for backup, the backup schedules are pushed to all the registered nodes of the AG. The schedules fire on all the AG nodes and the workload backup extensions on these nodes synchronize between themselves to decide which node can perform the backup. The node selection depends on the backup type and the backup preference as explained in section 1.
27
27
28
28
The selected node proceeds with the backup job, whereas the job triggered on the other nodes bails out, that is, it skips the job.
29
29
@@ -32,22 +32,22 @@ The selected node proceeds with the backup job, whereas the job triggered on the
32
32
33
33
## Register AG nodes to the Recovery Services vault
34
34
35
-
A Recovery Services vault supports backup of databases only from VMs in the same region and subscription as that of the vault.
35
+
A Recovery Services vault supports backup of databases only from VMs in the same region and subscription as of the vault.
36
36
37
-
-You must register the primary node to the vault (otherwise, full backups can't happen).
38
-
-If the backup preference is _secondary only_, then you need to register at least one secondary node to the vault (otherwise, log/copy-only full backups can't happen).
37
+
-Register the primary node to the vault (otherwise, full backups can't happen).
38
+
-Register at least one secondary node to the vault (otherwise, log/copy-only full backups can't happen) if the backup preference is _secondary only_.
39
39
40
-
Configuring backups for AG databases will fail with the error code _FabricSvcBackupPreferenceCheckFailedUserError_ if the above conditions aren't met.
40
+
Configuring backups for AG databases fail with the error code _FabricSvcBackupPreferenceCheckFailedUserError_ if the above conditions aren't met.
41
41
42
42
Let’s consider the following AG deployment as a reference.
43
43
44
44
:::image type="content" source="./media/backup-sql-server-on-availability-groups/ag-deployment.png" alt-text="Diagram for AG deployment as reference.":::
45
45
46
-
Based on the above sample AG deployment, following are various considerations:
46
+
Based on the given sample AG deployment, following are various considerations:
47
47
48
48
- As the primary node is in region 1 and subscription 1, the Recovery Services vault (Vault 1) must be in Region 1 and Subscription 1 for protecting this AG.
49
-
- VM3 can't be registered to Vault 1 as it's in a different subscription.
50
-
- VM4 can't be registered to Vault 1 as it's in a different region.
49
+
-`VM3` can't be registered to Vault 1 as it's in a different subscription.
50
+
-`VM4` can't be registered to Vault 1 as it's in a different region.
51
51
- If the backup preference is _secondary only_, VM1 (Primary) and VM2 (Secondary) must be registered to the Vault 1 (because full backups require the primary node and logs require a secondary node). For other backup preferences, VM1 (Primary) must be registered to Vault 1, VM2 is optional (because all backups can run on primary node).
52
52
- While VM3 could be registered to vault 2 in subscription 2 and the AG databases would then show up for protection in vault 2 but due to absence of the primary node in vault 2, configuring backups would fail.
53
53
- Similarly, while VM4 could be registered to vault 4 in region 2, configuring backups would fail since the primary node isn't registered in vault 4.
@@ -84,7 +84,7 @@ Recovery services vault doesn’t support cross-subscription or cross-region bac
84
84
85
85
- Full/differential backups will happen successfully only in the vault that has the primary node. These backups in other vaults will keep failing.
86
86
87
-
- Log backups will keep working in the previous vault till a log backup runs in the new vault (that's, in the vault where the new primary node is present) and _breaks_ the log chain for old vault.
87
+
- Log backups will keep working in the previous vault until a log backup runs in the new vault (that's, in the vault where the new primary node is present) and _breaks_ the log chain for old vault.
88
88
>[!Note]
89
89
>There's a hard limit of 15 days beyond which log backups will start failing.
90
90
@@ -106,7 +106,7 @@ As the primary node is in region and subscription, the usual steps to enable bac
106
106
1. Configure backups for the AG databases in Vault 2.
107
107
1. At this point:
108
108
1. The full/differential backups will fail in Vault 1 as none of the registered nodes can take this backup.
109
-
1. The log backups will succeed in Vault 1 till a log backup runs in Vault 2 and _breaks_ the log chain for Vault 1.
109
+
1. The log backups will succeed in Vault 1 until a log backup runs in Vault 2 and _breaks_ the log chain for Vault 1.
110
110
1. Failback the AG to VM1.
111
111
112
112
### Step 3: Enable backups in Region 2, Subscription 1 (Vault 4)
@@ -116,7 +116,7 @@ Same as Step 2.
116
116
## Backup an AG that spans Azure and on-premises
117
117
118
118
Azure Backup for SQL Server can’t be run on-premises. If the primary node is in Azure and the backup preference is satisfied by the nodes in Azure, you can follow the above guidance for multi-region AG to enable backups for the replicas in Azure.
119
-
If a failover to on-premises node happens, the full and differential backups in Azure will start failing. Log backups may continue till the log chain break happens/15 days pass.
119
+
If a failover to on-premises node happens, the full and differential backups in Azure will start failing. Log backups may continue until the log chain break happens/15 days pass.
Copy file name to clipboardExpand all lines: articles/backup/backup-support-matrix-mabs-dpm.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
title: MABS & System Center DPM support matrix
3
3
description: This article summarizes Azure Backup support when you use Microsoft Azure Backup Server (MABS) or System Center DPM to back up on-premises and Azure VM resources.
Copy file name to clipboardExpand all lines: articles/backup/backup-support-matrix-mars-agent.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
title: Support matrix for the MARS agent
3
3
description: This article summarizes Azure Backup support when you back up machines that are running the Microsoft Azure Recovery Services (MARS) agent.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments