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
The Azure extension for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] can perform backups automatically to local storage or network shares. Backups are written to the [default backup location](../../relational-databases/backup-restore/backup-devices-sql-server.md#BackupFileDiskPath) for the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] enabled by Azure Arc instance.
18
+
The Azure extension for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] can perform backups automatically to local storage or network shares. Backups are written to the [default backup location](../../relational-databases/backup-restore/backup-devices-sql-server.md#BackupFileDiskPath) for the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] enabled by Azure Arc instance.
17
19
18
20
This article explains how you can:
19
21
@@ -52,20 +54,20 @@ You can also run backups on a **default** schedule:
52
54
53
55
The following lists the levels of support for backup schedules:
54
56
55
-
- Instance level backups with a default schedule (available starting with [extension version 1.1.2284.7](release-notes.md#april-10-2023))
56
-
- Instance level backups with support for custom schedule (available starting with [extension version 1.1.2504.99](release-notes.md#november-14-2023))
57
-
- Database level backups with support for custom schedule (available starting with [extension version 1.1.2594.118](release-notes.md#march-12-2024))
57
+
- Instance level backups with a default schedule
58
+
- Instance level backups with support for custom schedule
59
+
- Database level backups with support for custom schedule
58
60
59
61
If both database and instance level backup schedule is set, database level schedule takes precedence over the instance level backup schedule. If you delete the database level backup schedule, the instance level backup schedule applies.
60
62
61
63
## Assign permissions
62
64
63
65
The backup service within the Azure extension for Arc-enabled SQL Server uses [NT AUTHORITY\SYSTEM] account to perform the backups. If you're [operating SQL Server enabled by Arc with least privilege](configure-least-privilege.md), A local Windows account - [NT Service\SQLServerExtension] - performs the backup.
If you use Azure extension for SQL Server [version 1.1.2504.99](release-notes.md#november-14-2023) or later, the necessary permissions are granted to [NT AUTHORITY\SYSTEM] automatically. You don't need to assign permissions manually.
70
+
If you use Azure extension for SQL Server version 1.1.2504.99 or later, the necessary permissions are granted to [NT AUTHORITY\SYSTEM] automatically. You don't need to assign permissions manually.
69
71
70
72
**For earlier extensions only**, follow the below steps to assign permission to [NT AUTHORITY\SYSTEM] account.
71
73
@@ -102,7 +104,7 @@ Automated backups are disabled by default.
102
104
103
105
After you assigned permissions, you can schedule automated backups. After the automated backups are configured, the Azure Extension for SQL Server initiates a backup to the default backup location.
104
106
105
-
The backups are native SQL Server backups, so all backup history is available in the backup related tables in themsdbdatabase.
107
+
The backups are native SQL Server backups, so all backup history is available in the backup related tables in the`msdb`database.
106
108
107
109
### Instance level
108
110
@@ -137,10 +139,10 @@ To enable automated backups using `az` CLI:
137
139
**Default schedule**
138
140
139
141
```azurecli
140
-
az sql server-arc backups-policy set --name <arc-server-name> --resource-group <resourcegroup> --default-policy
142
+
az sql server-arc backups-policy set --name <arc-server-name> --resource-group <resourcegroup> --default-policy
141
143
```
142
144
143
-
> [!NOTE]
145
+
> [!NOTE]
144
146
> Examples in this article use `<arc-server-name>` to identify the server name, as follows:
145
147
>
146
148
> - Default instance, replace: `<arc-server-name>` with the server name.
@@ -164,7 +166,7 @@ To enable automated backups using `az` CLI:
164
166
az sql server-arc backups-policy set --name MyArcServer_SQLServerPROD --resource-group MyResourceGroup --retention-days 24 --full-backup-days 7 --diff-backup-hours 24 --tlog-backup-mins 30
165
167
```
166
168
167
-
> [!NOTE]
169
+
> [!NOTE]
168
170
> If the backup retention day is set to 0, automated backup is disabled and no backups are taken.
169
171
170
172
---
@@ -192,30 +194,30 @@ Set retention period and frequency to meet business requirements. The retention
192
194
To enable automated backups on a database level using az CLI:
193
195
194
196
1. Disable any existing backup routines.
195
-
2. If necessary, add the arcdata extension:
197
+
1. If necessary, add the arcdata extension:
196
198
197
199
```azurecli
198
-
az extension add --name arcdata
200
+
az extension add --name arcdata
199
201
```
200
202
201
-
1. Configure either the default schedule or a custom schedule:
203
+
1. Configure either the default schedule or a custom schedule:
202
204
203
205
**Default schedule**
204
206
205
207
```azurecli
206
-
az sql db-arc backups-policy set --name <sql-database-name> --server <arc-server-name> --resource-group <resourcegroup> --default-policy
208
+
az sql db-arc backups-policy set --name <sql-database-name> --server <arc-server-name> --resource-group <resourcegroup> --default-policy
207
209
```
208
210
209
211
Example:
210
212
211
213
```azurecli
212
-
az sql db-arc backups-policy set --name MyDatabaseName--server MyArcServer_SQLServerPROD --resource-group MyResourceGroup --default-policy
214
+
az sql db-arc backups-policy set --name MyDatabaseName--server MyArcServer_SQLServerPROD --resource-group MyResourceGroup --default-policy
213
215
```
214
216
215
217
**Custom schedule**
216
218
217
219
```azurecli
218
-
az sql db-arc backups-policy set --name <sql-database-name> --server <arc-server-name> --resource-group <resourcegroup> --retention-days <number of days> --full-backup-days <num of days> --diff-backup-hours <12 or 24 hours> --tlog-backup-mins <number of minutes>
220
+
az sql db-arc backups-policy set --name <sql-database-name> --server <arc-server-name> --resource-group <resourcegroup> --retention-days <number of days> --full-backup-days <num of days> --diff-backup-hours <12 or 24 hours> --tlog-backup-mins <number of minutes>
219
221
```
220
222
221
223
Example:
@@ -226,40 +228,40 @@ To enable automated backups on a database level using az CLI:
226
228
227
229
---
228
230
229
-
## Disable automated backup
231
+
## Disable automated backup
230
232
231
-
If the backup retention day is set to 0, automated backup is disabled and no backups are taken, even though backup policy is retained. Setting the backup retention to a nonzero value enables the policy again.
233
+
If the backup retention day is set to 0, automated backup is disabled and no backups are taken, even though backup policy is retained. Setting the backup retention to a nonzero value enables the policy again.
232
234
233
-
This setting applies to both database and instance level backup. If database level backup schedule is disabled, no backups are taken for the database even if instance level backup is scheduled.
235
+
This setting applies to both database and instance level backup. If database level backup schedule is disabled, no backups are taken for the database even if instance level backup is scheduled.
234
236
235
-
## Delete automated backup
237
+
## Delete automated backup
236
238
237
239
From the portal for individual database level backup scheduling page, select **Revert backup policy to instance level** to delete the database level backup policy.
238
240
239
-
To delete instance level backup schedule, you can do it through CLI. Once deleted, no backup is taken either in instance level or database level. You must configure a new backup schedule to take the backup again.
241
+
To delete instance level backup schedule, you can do it through CLI. Once deleted, no backup is taken either in instance level or database level. You must configure a new backup schedule to take the backup again.
240
242
241
243
### Delete Instance Level Policy
242
244
243
245
```azurecli
244
-
az sql server-arc backups-policy delete --name <arc-server-name> --resource-group <resourcegroup>
246
+
az sql server-arc backups-policy delete --name <arc-server-name> --resource-group <resourcegroup>
245
247
```
246
248
247
249
Example:
248
250
249
251
```azurecli
250
-
az sql server-arc backups-policy delete --name MyArcServer_SQLServerPROD --resource-group MyResourceGroup
252
+
az sql server-arc backups-policy delete --name MyArcServer_SQLServerPROD --resource-group MyResourceGroup
@@ -316,7 +318,7 @@ When the built-in automated backups are enabled on an instance of [!INCLUDE [ssn
316
318
317
319
## Limitations
318
320
319
-
- Automatic backup to URL is not currently available.
321
+
- Automatic backup to URL isn't currently available.
320
322
- The user databases need to be in full recovery model for the backups to be performed. Databases that aren't in full recovery model aren't automatically backed up.
321
323
- Automated backups are currently not supported for Always On failover cluster instances (FCI).
322
324
- Automated backups aren't supported on any instance that hosts an availability group (AG) replica.
@@ -325,5 +327,5 @@ When the built-in automated backups are enabled on an instance of [!INCLUDE [ssn
325
327
## Related tasks
326
328
327
329
-[Restore to a point-in-time](point-in-time-restore.md)
0 commit comments