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
title: Back up SQL Server workloads on Azure Stack
3
3
description: In this article, learn how to configure Microsoft Azure Backup Server (MABS) to protect SQL Server databases on Azure Stack.
4
-
ms.topic: conceptual
5
-
ms.date: 06/08/2018
4
+
ms.topic: how-to
5
+
ms.date: 01/18/2023
6
+
author: jyothisuri
7
+
ms.author: jsuri
8
+
ms.service: backup
9
+
ms.custom: engagement-fy23
6
10
---
11
+
7
12
# Back up SQL Server on Azure Stack
8
13
9
-
Use this article to configure Microsoft Azure Backup Server (MABS) to protect SQL Server databases on Azure Stack.
14
+
This article describes how to configure Microsoft Azure Backup Server (MABS) to protect SQL Server databases on Azure Stack.
15
+
16
+
## SQL Server databases protection workflow
10
17
11
-
The management of SQL Server database backup to Azure and recovery from Azure involves three steps:
18
+
The management of SQL Server database backup to Azure and recovery from Azure involves:
12
19
13
20
1. Create a backup policy to protect SQL Server databases
14
21
2. Create on-demand backup copies
15
22
3. Recover the database from Disks, and from Azure
16
23
17
24
## Prerequisites and limitations
18
25
19
-
* If you have a database with files on a remote file share, protection will fail with Error ID 104. MABS doesn't support protection for SQL Server data on a remote file share.
26
+
* If you've a database with files on a remote file share, protection will fail with Error ID 104. MABS doesn't support protection for SQL Server data on a remote file share.
20
27
* MABS can't protect databases that are stored on remote SMB shares.
21
28
* Ensure that the [availability group replicas are configured as read-only](/sql/database-engine/availability-groups/windows/configure-read-only-access-on-an-availability-replica-sql-server).
22
29
* You must explicitly add the system account **NTAuthority\System** to the Sysadmin group on SQL Server.
@@ -39,84 +46,83 @@ The management of SQL Server database backup to Azure and recovery from Azure in
39
46
* If the backup fails on the selected node, then the backup operation fails.
40
47
* Recovery to the original location isn't supported.
41
48
* SQL Server 2014 or above backup issues:
42
-
* SQL server 2014 added a new feature to create a [database for on-premises SQL Server in Windows Azure Blob storage](/sql/relational-databases/databases/sql-server-data-files-in-microsoft-azure). MABS can't be used to protect this configuration.
49
+
* SQL server 2014 added a new feature to create a [database for on-premises SQL Server on Microsoft Azure Blob storage](/sql/relational-databases/databases/sql-server-data-files-in-microsoft-azure). MABS can't be used to protect this configuration.
43
50
* There are some known issues with "Prefer secondary" backup preference for the SQL Always On option. MABS always takes a backup from secondary. If no secondary can be found, then the backup fails.
44
51
45
52
## Before you start
46
53
47
54
[Install and prepare Azure Backup Server](backup-mabs-install-azure-stack.md).
48
55
49
-
## Create a backup policy to protect SQL Server databases to Azure
56
+
## Create a backup policy
57
+
58
+
To create a backup policy to protect SQL Server databases to Azure, follow these steps:
50
59
51
60
1. On the Azure Backup Server UI, select the **Protection** workspace.
52
61
53
62
2. On the tool ribbon, select **New** to create a new protection group.
56
65
57
66
Azure Backup Server starts the Protection Group wizard, which leads you through creating a **Protection Group**. Select **Next**.
58
67
59
-
3.In the **Select Protection Group Type** screen, select **Servers**.
68
+
3.On the **Select Protection Group Type** screen, select **Servers**.
60
69
61
-
70
+
62
71
63
-
4.In the **Select Group Members** screen, the Available members list displays the various data sources. Select **+** to expand a folder and reveal the subfolders. Select the checkbox to select an item.
72
+
4.On the **Select Group Members** screen, the Available members list displays the various data sources. Select **+** to expand a folder and reveal the subfolders. Select the checkbox to select an item.
66
75
67
76
All selected items appear in the Selected members list. After selecting the servers or databases you want to protect, select **Next**.
68
77
69
-
5.In the **Select Data Protection Method** screen, provide a name for the protection group and select the **I want online Protection** checkbox.
78
+
5.On the **Select Data Protection Method** screen, provide a name for the protection group and select the **I want online Protection** checkbox.
70
79
71
-
80
+
72
81
73
-
6.In the **Specify Short-Term Goals** screen, include the necessary inputs to create backup points to disk, and select **Next**.
82
+
6.On the **Specify Short-Term Goals** screen, include the necessary inputs to create backup points to disk, and select **Next**.
74
83
75
84
In the example, **Retention range** is **5 days**, **Synchronization frequency** is once every **15 minutes**, which is the backup frequency. **Express Full Backup** is set to **8:00 P.M**.
78
87
79
88
> [!NOTE]
80
89
> In the example shown, at 8:00 PM every day a backup point is created by transferring the modified data from the previous day’s 8:00 PM backup point. This process is called **Express Full Backup**. Transaction logs are synchronized every 15 minutes. If you need to recover the database at 9:00 PM, the point is created from the logs from the last express full backup point (8PM in this case).
81
-
>
82
-
>
83
90
84
91
7. On the **Review disk allocation** screen, verify the overall storage space available, and the potential disk space. Select **Next**.
85
92
86
-
8.In the **Choose Replica Creation Method**, choose how to create your first recovery point. You can transfer the initial backup manually (off network) to avoid bandwidth congestion or over the network. If you choose to wait to transfer the first backup, you can specify the time for the initial transfer. Select **Next**.
93
+
8.On the **Choose Replica Creation Method**, choose how to create your first recovery point. You can transfer the initial backup manually (off network) to avoid bandwidth congestion or over the network. If you choose to wait to transfer the first backup, you can specify the time for the initial transfer. Select **Next**.
89
96
90
97
The initial backup copy requires transferring the entire data source (SQL Server database) from production server (SQL Server computer) to Azure Backup Server. This data might be large, and transferring the data over the network could exceed bandwidth. For this reason, you can choose to transfer the initial backup: **Manually** (using removable media) to avoid bandwidth congestion, or **Automatically over the network** (at a specified time).
91
98
92
99
Once the initial backup is complete, the rest of the backups are incremental backups on the initial backup copy. Incremental backups tend to be small and are easily transferred across the network.
93
100
94
101
9. Choose when you want the consistency check to run and select **Next**.
97
104
98
105
Azure Backup Server performs a consistency check on the integrity of the backup point. Azure Backup Server calculates the checksum of the backup file on the production server (SQL Server computer in this scenario) and the backed-up data for that file. If there's a conflict, it's assumed the backed-up file on Azure Backup Server is corrupt. Azure Backup Server rectifies the backed-up data by sending the blocks corresponding to the checksum mismatch. Because consistency checks are performance-intensive, you can schedule the consistency check or run it automatically.
99
106
100
107
10. To specify online protection of the datasources, select the databases to be protected to Azure and select **Next**.
103
110
104
111
11. Choose backup schedules and retention policies that suit the organization policies.
105
112
106
-
113
+
107
114
108
115
In this example, backups are taken once a day at 12:00 PM and 8 PM (bottom part of the screen)
109
116
110
117
> [!NOTE]
111
118
> It’s a good practice to have a few short-term recovery points on disk, for quick recovery. These recovery points are used for operational recovery. Azure serves as a good offsite location with higher SLAs and guaranteed availability.
112
-
>
113
-
>
119
+
114
120
115
121
**Best Practice**: If you schedule backups to Azure to start after the local disk backups complete, the latest disk backups are always copied to Azure.
116
122
117
123
12. Choose the retention policy schedule. The details on how the retention policy works are provided at [Use Azure Backup to replace your tape infrastructure article](backup-azure-backup-cloud-as-tape.md).
120
126
121
127
In this example:
122
128
@@ -128,52 +134,54 @@ The management of SQL Server database backup to Azure and recovery from Azure in
128
134
129
135
14. Once you review the policy details in the **Summary** screen, select **Create group** to complete the workflow. You can select **Close** and monitor the job progress in Monitoring workspace.
130
136
131
-
137
+
138
+
139
+
## Run an on-demand backup
132
140
133
-
## On-demand backup of a SQL Server database
141
+
A *recovery point* is created only when the first backup occurs. After creating a backup policy, you can trigger the creation of a recovery point manually, rather than waiting for the scheduler to take the backup.
134
142
135
-
While the previous steps created a backup policy, a “recovery point” is created only when the first backup occurs. Rather than waiting for the scheduler to kick in, the steps below trigger the creation of a recovery point manually.
143
+
To run an on-demand backup of a SQL Server database, follow these steps:
136
144
137
145
1. Wait until the protection group status shows **OK** for the database before creating the recovery point.
138
146
139
-
140
-
2. Right-click on the database and select **Create Recovery Point**.
147
+
148
+
2. Right-click the database and select **Create Recovery Point**.
149
157
150
-
## Recover a SQL Server database from Azure
158
+
## Recover the database from Azure
151
159
152
-
The following steps are required to recover a protected entity (SQL Server database) from Azure.
160
+
To recover a protected entity (SQL Server database) from Azure, follow these steps:
153
161
154
162
1. Open the Azure Backup Server Management Console. Navigate to **Recovery** workspace where you can see the protected servers. Browse the required database (in this case ReportServer$MSDPM2012). Select a **Recovery from** time that's specified as an **Online** point.
157
165
2. Right-click the database name and select **Recover**.
158
166
159
-
167
+
160
168
3. MABS shows the details of the recovery point. Select **Next**. To overwrite the database, select the recovery type **Recover to original instance of SQL Server**. Select **Next**.
161
169
162
-
170
+
163
171
164
172
In this example, MABS recovers the database to another SQL Server instance, or to a standalone network folder.
165
173
166
-
4.In the **Specify Recovery options** screen, you can select the recovery options like Network bandwidth usage throttling to throttle the bandwidth used by recovery. Select **Next**.
174
+
4.On the **Specify Recovery options** screen, you can select the recovery options like Network bandwidth usage throttling to throttle the bandwidth used by recovery. Select **Next**.
167
175
168
-
5.In the **Summary** screen, you see all the recovery configurations provided so far. Select **Recover**.
176
+
5.On the **Summary** screen, you see all the recovery configurations provided so far. Select **Recover**.
169
177
170
178
The Recovery status shows the database being recovered. You can select **Close** to close the wizard and view the progress in the **Monitoring** workspace.
0 commit comments