Skip to content

Commit d549aa2

Browse files
authored
Update manage-backup.md - custom domain during custom backup restore
custom domain handling during custom backup restore is different with automatic backup restore.
1 parent 97359f8 commit d549aa2

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/app-service/manage-backup.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -329,6 +329,8 @@ The following table shows which app configurations are restored when you choose
329329
330330
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.
331331
332+
Each backup contains a .zip file with backup data and an .xml file {siteName}-{dateTime}.xml, which lists the contents, including [custom domains](app-service-web-tutorial-custom-domain.md). When restoring a custom backup, custom domains from the .xml file will be added to the destination app if no DNS conflict exists (i.e., the domain is available for binding), and if the destination app has different custom domains than the .xml file's custom domain list, those custom domains will be removed.
333+
332334
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).
333335
334336
### Why is my linked database not backed up?

0 commit comments

Comments
 (0)