new docs for backup UI

Author: cephalin

.openpublishing.publish.config.json

@@ -884,6 +884,7 @@
     ".openpublishing.redirection.defender-for-iot.json",
     ".openpublishing.redirection.healthcare-apis.json",
     ".openpublishing.redirection.iot-hub.json",
+    ".openpublishing.redirection.app-service.json",
     ".openpublishing.redirection.key-vault.json",
     ".openpublishing.redirection.media-services.json",
     ".openpublishing.redirection.security-benchmark.json",

.openpublishing.redirection.app-service.json

@@ -0,0 +1,19 @@
+{
+  "redirections": [
+    {
+      "source_path_from_root": "/articles/app-service-web/web-sites-restore.md",
+      "redirect_url": "/azure/app-service/manage-backup",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/app-service/web-sites-restore.md",
+      "redirect_url": "/azure/app-service/manage-backup",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/app-service/app-service-web-restore-snapshots.md",
+      "redirect_url": "/azure/app-service/manage-backup",
+      "redirect_document_id": false
+    }
+  ]
+}

.openpublishing.redirection.json

@@ -4933,11 +4933,6 @@
       "redirect_url": "/azure/app-service/web-sites-monitor",
       "redirect_document_id": false
     },
-    {
-      "source_path_from_root": "/articles/app-service-web/web-sites-restore.md",
-      "redirect_url": "/azure/app-service/web-sites-restore",
-      "redirect_document_id": false
-    },
     {
       "source_path_from_root": "/articles/app-service-web/web-sites-traffic-manager.md",
       "redirect_url": "/azure/app-service/web-sites-traffic-manager",

articles/app-service/app-service-web-restore-snapshots.md

@@ -37,9 +37,9 @@ App Service Environment v3 uses Isolated v2 App Service plans that are priced an
 
 ## Back up and restore
 
-The [back up](../manage-backup.md) and [restore](../web-sites-restore.md) feature allows you to keep your app configuration, file content, and database connected to your app when migrating to your new environment. Make sure you review the [requirements and restrictions](../manage-backup.md#requirements-and-restrictions) of this feature.
+The [back up](../manage-backup.md) and [restore](../manage-backup.md) feature allows you to keep your app configuration, file content, and database connected to your app when migrating to your new environment. Make sure you review the [requirements and restrictions](../manage-backup.md#requirements-and-restrictions) of this feature.
 
-The step-by-step instructions in the current documentation for [back up](../manage-backup.md) and [restore](../web-sites-restore.md) should be sufficient to allow you to use this feature. When restoring, the **Storage** option lets you select any backup ZIP file from any existing Azure Storage account container in your subscription. A sample of a restore configuration is given in the following screenshot.
+The step-by-step instructions in the current documentation for [back up](../manage-backup.md) and [restore](../manage-backup.md) should be sufficient to allow you to use this feature. When restoring, the **Storage** option lets you select any backup ZIP file from any existing Azure Storage account container in your subscription. A sample of a restore configuration is given in the following screenshot.
 
 ![back up and restore sample](./media/migration/back-up-restore-sample.png)
 

articles/app-service/environment/migration-alternatives.md

@@ -43,7 +43,7 @@ Certain resources, such as imported certificates or hybrid connections, contain
 
 1. [Create a back up of the source app](manage-backup.md).
 1. [Create an app in a new App Service plan, in the target region](app-service-plan-manage.md#create-an-app-service-plan).
-2. [Restore the back up in the target app](web-sites-restore.md)
+2. [Restore the back up in the target app](manage-backup.md)
 2. If you use a custom domain, [bind it preemptively to the target app](manage-custom-dns-migrate-domain.md#bind-the-domain-name-preemptively) with `awverify.` and [enable the domain in the target app](manage-custom-dns-migrate-domain.md#enable-the-domain-for-your-app).
 3. Configure everything else in your target app to be the same as the source app and verify your configuration.
 4. When you're ready for the custom domain to point to the target app, [remap the domain name](manage-custom-dns-migrate-domain.md#remap-the-active-dns-name).

articles/app-service/manage-backup.md

@@ -321,12 +321,8 @@
       items:
         - name: Manage the hosting plan
           href: app-service-plan-manage.md
-        - name: Back up an app
+        - name: Backup and restore
           href: manage-backup.md
-        - name: Restore a backup
-          href: web-sites-restore.md
-        - name: Restore a snapshot
-          href: app-service-web-restore-snapshots.md
         - name: Clone an app
           href: app-service-web-app-cloning.md
         - name: Restore deleted App Service

articles/app-service/manage-move-across-regions.md

@@ -97,7 +97,7 @@ The high-level idea as represented above is as follows:
 
 1. Set up two parallel [QnA Maker services](set-up-qnamaker-service-azure.md) in [Azure paired regions](../../../availability-zones/cross-region-replication-azure.md).
 
-1. [Backup](../../../app-service/manage-backup.md) your primary QnA Maker App service and [restore](../../../app-service/web-sites-restore.md) it in the secondary setup. This will ensure that both setups work with the same hostname and keys.
+1. [Backup](../../../app-service/manage-backup.md) your primary QnA Maker App service and [restore](../../../app-service/manage-backup.md) it in the secondary setup. This will ensure that both setups work with the same hostname and keys.
 
 1. Keep the primary and secondary Azure search indexes in sync. Use the GitHub sample [here](https://github.com/pchoudhari/QnAMakerBackupRestore) to see how to backup-restore Azure indexes.