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/app-service/manage-backup.md
+25-19Lines changed: 25 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,12 @@ There are two types of backups in App Service. Automatic backups are created for
148
148
149
149
1. Configure the backup schedule as desired and then select **Configure**.
150
150
151
-
#### Back up and restore a linked database
151
+
### Back up and restore a linked database
152
+
153
+
> [!NOTE]
154
+
> Custom backups with linked databases for App Service support only **Single Server SKUs** of Azure Database for MySQL and PostgreSQL. Upgrading linked databases to **Flexible Server** may cause backups to fail. Use native database backup tools to prevent data loss. Standalone MySQL and PostgreSQL servers (e.g., on VMs) are unaffected by the Single Server SKU retirement.
155
+
> For retirement details, see [MySQL Single Server retirement](/azure/mysql/migrate/whats-happening-to-mysql-single-server.md) and [PostgreSQL Single Server retirement](/azure/postgresql/migrate/whats-happening-to-postgresql-single-server).
156
+
>
152
157
153
158
Custom backups can include linked databases (except when the backup is configured over Azure Virtual Network). To make sure your backup includes a linked database, do the following:
154
159
@@ -280,15 +285,15 @@ For samples, see:
280
285
- [Where are the automatic backups stored?](#where-are-the-automatic-backups-stored)
281
286
- [How do I stop an automatic backup?](#how-do-i-stop-an-automatic-backup)
282
287
283
-
#### Are the backups incremental updates or complete backups?
288
+
### Are the backups incremental updates or complete backups?
284
289
285
290
Each backup is a complete offline copy of your app, not an incremental update.
286
291
287
-
#### Does Azure Functions support automatic backups?
292
+
### Does Azure Functions support automatic backups?
288
293
289
294
Automatic backups are available for Azure Functions in [dedicated (App Service)](../azure-functions/dedicated-plan.md) **Basic**, **Standard**, and **Premium** tiers. Automatic backups aren't supported for function apps in the [**Consumption**](../azure-functions/consumption-plan.md) or [**Elastic Premium**](../azure-functions/functions-premium-plan.md) pricing tiers.
290
295
291
-
#### What's included in an automatic backup?
296
+
### What's included in an automatic backup?
292
297
293
298
The following table shows which content is backed up in an automatic backup:
294
299
@@ -317,21 +322,16 @@ The following table shows which app configurations are restored when you choose
317
322
|Associated [deployment slots](deploy-staging-slots.md)| No |
318
323
|Any linked database that [custom backup](#whats-included-in-a-custom-backup) supports| No |
319
324
320
-
#### What's included in a custom backup?
325
+
### What's included in a custom backup?
321
326
322
327
A custom backup (on-demand backup or scheduled backup) includes all content and configuration that's included in an [automatic backup](#whats-included-in-an-automatic-backup), plus any linked database, up to the allowable maximum size.
323
328
324
329
When [backing up over Azure Virtual Network](#back-up-and-restore-over-azure-virtual-network), you can't [back up the linked database](#back-up-and-restore-a-linked-database).
325
330
326
-
#### Why is my linked database not backed up?
331
+
### Why is my linked database not backed up?
327
332
328
-
> [!NOTE]
329
-
> This is an important note related to the retirement of [Azure Database for MySQL - Single Server](/azure/mysql/migrate/whats-happening-to-mysql-single-server.md) and [Azure Database for PostgreSQL - Single Server](azure/postgresql/migrate/whats-happening-to-postgresql-single-server.md). App Service custom backups with linked databases only support **Single Server SKUs** for Azure Database for MySQL and Azure DB for PostgreSQL. This means that custom backups with linked databases for Azure Database for *MySQL - Flexible Server* and Azure Database for *PostgreSQL - Flexible Server* may stop working. If you've already upgraded or plan to upgrade linked databases for these services, it's strongly advised to use the respective database backup and restore tools to avoid potential data loss.
330
-
>
331
-
> - Azure Database for MySQL: [Back up and restore](/azure/mysql/flexible-server/concepts-backup-restore).
332
-
> - Azure Database for PostgreSQL [Back up and restore](/azure/postgresql/flexible-server/concepts-backup-restore).
333
-
>
334
-
> Custom backups for App Service web apps that include linked databases based on standalone deployments of MySQL and PostgreSQL database servers (for example standalone database servers running on a VM), may continue to function and are not affected by the Single Server SKU retirements on Azure Database for MySQL - Single Server and Azure Database for PostgreSQL - Single Server.
333
+
> [!NOTE]
334
+
> Custom backups with linked databases for App Service support only **Single Server SKUs** of Azure Database for MySQL and PostgreSQL. Upgrading linked databases to **Flexible Server** may cause backups to fail. Use native database backup tools to prevent data loss. Standalone MySQL and PostgreSQL servers (e.g., on VMs) are unaffected by the Single Server SKU retirement.
335
335
>
336
336
337
337
Linked databases are backed up only for custom backups, up to the allowable maximum size. If the maximum backup size (10 GB) or the maximum database size (4 GB) is exceeded, your backup fails. Here are a few common reasons why your linked database isn't backed up:
@@ -340,15 +340,21 @@ Linked databases are backed up only for custom backups, up to the allowable maxi
340
340
- Backup of [TLS-enabled Azure Database for PostgreSQL](/azure/postgresql/concepts-ssl-connection-security) isn't supported. If a backup is configured, you get backup failures.
341
341
- In-app MySQL databases are automatically backed up without any configuration. If you make manual settings for in-app MySQL databases, such as adding connection strings, the backups might not work correctly.
342
342
343
-
#### What happens if the backup size exceeds the allowable maximum?
343
+
For back up and restore of Flexible Servers and standalone servers, use the respective database documentation:
344
+
- [Azure Database for MySQL: Back up and restore](/azure/mysql/flexible-server/concepts-backup-restore)
345
+
- [Azure Database for PostgreSQL: Back up and restore](/azure/postgresql/flexible-server/concepts-backup-restore)
346
+
- [MySQL server: Back up and restore](https://dev.mysql.com/doc/refman/8.4/en/backup-and-recovery.html).
347
+
- [PostgreSQL server: Back up and restore](https://www.postgresql.org/docs/current/backup-dump.html).
348
+
349
+
### What happens if the backup size exceeds the allowable maximum?
344
350
345
351
Automatic backups can't be restored if the backup size exceeds the maximum size. Similarly, custom backups fail if the maximum backup size or the maximum database size is exceeded. To reduce your storage size, consider moving files like logs, images, audio, and videos to Azure Storage, for example.
346
352
347
-
#### Can I use a storage account that has security features enabled?
353
+
### Can I use a storage account that has security features enabled?
348
354
349
355
You can back up to a firewall-protected storage account if it's part of the same virtual network topology as your app. See [Back up and restore over Azure Virtual Network](#back-up-and-restore-over-azure-virtual-network).
350
356
351
-
#### How do I restore to an app in a different subscription?
357
+
### How do I restore to an app in a different subscription?
352
358
353
359
1. Make a custom backup to an Azure Storage container.
354
360
1. [Download the backup ZIP file](../storage/blobs/storage-quickstart-blobs-portal.md) to your local machine.
@@ -359,15 +365,15 @@ You can back up to a firewall-protected storage account if it's part of the same
359
365
1. In **Name**, select **Browse** and select the downloaded ZIP file.
360
366
1. Configure the rest of the sections as described in [Restore a backup](#restore-a-backup).
361
367
362
-
#### How do I restore to an app in the same subscription but in a different region?
368
+
### How do I restore to an app in the same subscription but in a different region?
363
369
364
370
The steps are the same as in [How do I restore to an app in a different subscription?](#how-do-i-restore-to-an-app-in-a-different-subscription).
365
371
366
-
#### Where are the automatic backups stored?
372
+
### Where are the automatic backups stored?
367
373
368
374
Automatic backups are stored in the same datacenter as the App Service. They shouldn't be relied upon as your disaster recovery plan.
369
375
370
-
#### How do I stop an automatic backup?
376
+
### How do I stop an automatic backup?
371
377
372
378
You can't stop automatic backups. The automatic backup is stored on the platform and has no effect on the underlying app instance or its storage.
0 commit comments