additional offline docs

David Curwin · David Curwin · commit b7328f06994c · 2020-01-28T09:24:12.000+02:00
diff --git a/articles/backup/backup-azure-about-mars.md b/articles/backup/backup-azure-about-mars.md
@@ -53,8 +53,7 @@ The MARS agent supports the following restore scenarios:
 ### Additional scenarios
 -	**Back up specific files and folders within Azure virtual machines**: The primary method for backing up Azure virtual machines (VMs) is to use an Azure Backup extension on the VM. The extension backs up the entire VM. If you want to back up specific files and folders within a VM, you can install the MARS agent in the Azure VMs. For more information, see [Architecture: Built-in Azure VM Backup](https://docs.microsoft.com/azure/backup/backup-architecture#architecture-built-in-azure-vm-backup).
 
--	**Offline seeding**: Initial full backups of data to Azure typically transfer large amounts of data and require more network bandwidth. Subsequent backups transfer only the delta, or incremental, amount of data. Azure Backup compresses the initial backups. Through the process of *offline seeding*, Azure Backup can use disks to upload the compressed initial backup data offline to Azure. For more information, see [Offline-backup workflow for DPM and Azure Backup Server](https://docs.microsoft.com/azure/backup/backup-azure-backup-server-import-export-).
-
+-	**Offline seeding**: Initial full backups of data to Azure typically transfer large amounts of data and require more network bandwidth. Subsequent backups transfer only the delta, or incremental, amount of data. Azure Backup compresses the initial backups. Through the process of *offline seeding*, Azure Backup can use disks to upload the compressed initial backup data offline to Azure. For more information, see [Azure Backup offline-backup using Azure Data Box](offline-backup-azure-data-box.md).
 
 ## Next steps
 [MARS agent support matrix](https://docs.microsoft.com/azure/backup/backup-support-matrix-mars-agent)
diff --git a/articles/backup/backup-azure-backup-server-import-export-.md b/articles/backup/backup-azure-backup-server-import-export-.md
@@ -3,7 +3,7 @@ title: Offline backup for DPM and Azure Backup Server
 description: Azure Backup enables you to send data off the network using the Azure Import/Export service. This article explains the offline backup workflow for DPM and Azure Backup Server (MABS).
 ms.reviewer: saurse
 ms.topic: conceptual
-ms.date: 05/08/2018
+ms.date: 1/28/2020
 ---
 # Offline-backup workflow for DPM and Azure Backup Server
 
@@ -50,14 +50,42 @@ Ensure that the following prerequisites are met before initiating the Offline Ba
     | United States | [Link](https://portal.azure.us#blade/Microsoft_Azure_ClassicResources/PublishingProfileBlade) |
     | China | [Link](https://portal.azure.cn/#blade/Microsoft_Azure_ClassicResources/PublishingProfileBlade) |
 
-* An Azure Storage account with *classic* deployment model has been created in the subscription from which you downloaded the publish settings file as shown below:
+* An Azure Storage account with *Resource Manager* deployment model has been created in the subscription from which you downloaded the publish settings file as shown below:
 
-  ![Creating a classic storage account](./media/backup-azure-backup-import-export/storageaccountclassiccreate.png)
+  ![Creating a storage account with Resource Manager development](./media/backup-azure-backup-import-export/storage-account-resource-manager.png)
 
 * A staging location, which might be a network share or any additional drive on the computer, internal or external, with enough disk space to hold your initial copy, is created. For example, if you are trying to back up a 500-GB file server, ensure that the staging area is at least 500 GB. (A smaller amount is used due to compression.)
 * With regards to disks that will be sent to Azure, ensure that only 2.5 inch SSD, or 2.5-inch or 3.5-inch SATA II/III internal hard drives are used. You can use hard drives up to 10 TB. Check the [Azure Import/Export service documentation](../storage/common/storage-import-export-requirements.md#supported-hardware) for the latest set of drives that the service supports.
 * The SATA drives have to be connected to a computer (referred to as a *copy computer*) from where the copy of backup data from the *staging location* to the SATA drives is done. Ensure that BitLocker is enabled on the *copy computer*
 
+## Prepare the Server for the Offline Backup process
+
+>[!NOTE]
+> If you cannot find the listed utilities such as *AzureOfflineBackupCertGen.exe* in your installation of the MARS agent, write to AskAzureBackupTeam@microsoft.com to get access to them.
+
+* Open an elevated command prompt on the server and run the following command:
+
+    ```cmd
+    AzureOfflineBackupCertGen.exe CreateNewApplication SubscriptionId:<Subs ID>
+    ```
+
+    The tool will create an Azure Offline Backup AD Application if one does not exist.
+
+    If an Application already exists, this executable will ask you to manually upload the certificate to the application in the tenant. Follow the steps below in this section to upload the certificate manually to the app.
+
+* The AzureOfflineBackup.exe tool will generate an OfflineApplicationParams.xml file.  Copy this file to the server with MABS or DPM.
+* Install the [latest MARS agent](https://aka.ms/azurebackup_agent) on the DPM/Venus server.
+* Register the server to Azure.
+* Run the following command:
+
+    ```cmd
+    AzureOfflineBackupCertGen.exe AddRegistryEntries SubscriptionId:<subscriptionid> xmlfilepath:<path of the OfflineApplicationParams.xml file>  storageaccountname:<storageaccountname configured with Azure Data Box>
+    ```
+
+    For more information on the supported options for the AzureOfflineBackupCertGen.exe, see *ReadMeAzureCertGen.txt* and *addRegistry.PNG*
+
+* The command above will create the file `C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch\MicrosoftBackupProvider\OfflineApplicationParams_Storageaccountname.xml`
+
 ## Workflow
 
 The information in this section helps you complete the offline-backup workflow so that your data can be delivered to an Azure datacenter and uploaded to Azure Storage. If you have questions about the Import service or any aspect of the process, see the [Import service overview](../storage/common/storage-import-export-service.md) documentation referenced earlier.
@@ -212,4 +240,3 @@ At the time of the next scheduled backup, Azure Backup performs incremental back
 ## Next steps
 
 * For any questions on the Azure Import/Export workflow, refer to [Use the Microsoft Azure Import/Export service to transfer data to Blob storage](../storage/common/storage-import-export-service.md).
-
diff --git a/articles/backup/backup-azure-backup-sql.md b/articles/backup/backup-azure-backup-sql.md
@@ -97,7 +97,7 @@ Before you begin, ensure that all the [prerequisites](backup-azure-dpm-introduct
 14. Click **Next** and select the appropriate option for transferring the initial backup copy to Azure. You can choose **Automatically over the network** or **Offline Backup**.
 
     * **Automatically over the network** transfers the backup data to Azure as per the schedule chosen for backup.
-    * How **Offline Backup** works is explained at [Offline Backup workflow in Azure Backup](backup-azure-backup-import-export.md).
+    * How **Offline Backup** works is explained at [Overview of Offline Backup](offline-backup-overview.md).
 
     Choose the relevant transfer mechanism to send the initial backup copy to Azure and click **Next**.
 15. Once you review the policy details in the **Summary** screen, click on the **Create group** button to complete the workflow. You can click the **Close** button and monitor the job progress in Monitoring workspace.
diff --git a/articles/backup/backup-azure-sql-mabs.md b/articles/backup/backup-azure-sql-mabs.md
@@ -95,7 +95,7 @@ Before you begin, ensure that you have [installed and prepared the Azure Backup
 14. Click **Next** and select the appropriate option for transferring the initial backup copy to Azure. You can choose **Automatically over the network** or **Offline Backup**.
 
     * **Automatically over the network** transfers the backup data to Azure as per the schedule chosen for backup.
-    * How **Offline Backup** works is explained at [Offline Backup workflow in Azure Backup](backup-azure-backup-import-export.md).
+    * How **Offline Backup** works is explained at [Overview of Offline Backup](offline-backup-overview.md).
 
     Choose the relevant transfer mechanism to send the initial backup copy to Azure and click **Next**.
 15. Once you review the policy details in the **Summary** screen, click on the **Create group** button to complete the workflow. You can click the **Close** button and monitor the job progress in Monitoring workspace.
diff --git a/articles/backup/backup-configure-vault.md b/articles/backup/backup-configure-vault.md
@@ -214,7 +214,7 @@ Create a policy as follows:
     ![Retention example](./media/backup-configure-vault/retention-example.png)
 
 
-11. In **Choose Initial Backup Type** decide if you want to take the initial backup over the network or use offline backup (for more information on offline backup refer, see this [article](backup-azure-backup-import-export.md)). To take the initial backup over the network, select **Automatically over the network** and click **Next**.
+11. In **Choose Initial Backup Type** decide if you want to take the initial backup over the network or use offline backup (for more information on offline backup refer, see this [article](offline-backup-azure-data-box.md)). To take the initial backup over the network, select **Automatically over the network** and click **Next**.
 
     ![initial Backup Type](./media/backup-azure-manage-mars/choose-initial-backup-type.png)
 
@@ -241,7 +241,7 @@ You can run an initial backup automatically over the network, or offline. Offlin
 5. At the datacenter, the disk data is copied to an Azure storage account.
 6. Azure Backup copies the data from the storage account to the vault, and incremental backups are scheduled.
 
-[Learn more](backup-azure-backup-import-export.md) about offline seeding.
+[Learn more](offline-backup-azure-data-box.md) about offline seeding.
 
 ### Enable network throttling
 
diff --git a/articles/backup/backup-mabs-system-state-and-bmr.md b/articles/backup/backup-mabs-system-state-and-bmr.md
@@ -135,7 +135,7 @@ Set up a protection group as described in [Deploy protection groups](https://doc
 
 12. On the **Specify Online Retention Policy** page, select how the recovery points that are created from the daily, weekly, monthly, and yearly backups are retained in Azure.
 
-13. On the **Choose Online Replication** page, select how the initial full replication of data occurs. You can replicate over the network or do an offline backup (offline seeding). Offline backup uses the Azure Import feature. For more information, see [Offline backup workflow in Azure Backup](backup-azure-backup-import-export.md).
+13. On the **Choose Online Replication** page, select how the initial full replication of data occurs. You can replicate over the network or do an offline backup (offline seeding). Offline backup uses the Azure Import feature. For more information, see [Offline backup workflow in Azure Backup](offline-backup-azure-data-box.md).
 
 14. On the  **Summary** page, review your settings. After you select **Create Group**, initial replication of the data occurs. When data replication finishes, on the **Status** page, the protection group status is **OK**. Backup then takes place per the protection group settings.
 
diff --git a/articles/backup/media/backup-azure-backup-import-export/storage-account-resource-manager.png b/articles/backup/media/backup-azure-backup-import-export/storage-account-resource-manager.png
diff --git a/articles/backup/media/offline-backup-overview/azure-backup-databox-architecture.png b/articles/backup/media/offline-backup-overview/azure-backup-databox-architecture.png
diff --git a/articles/backup/media/offline-backup-overview/azure-backup-import-export.png b/articles/backup/media/offline-backup-overview/azure-backup-import-export.png
diff --git a/articles/backup/offline-backup-azure-data-box.md b/articles/backup/offline-backup-azure-data-box.md
@@ -328,4 +328,4 @@ From the server you are trying to configure offline backup, perform the followin
 
 ## Questions
 
-For any questions or clarifications, regarding any issues faced, reach out to [saurse@microsoft.com](mailto:saurse@microsoft.com)
+For any questions or clarifications, regarding any issues faced, reach out to [AskAzureBackupTeam@microsoft.com](mailto:AskAzureBackupTeam@microsoft.com)
diff --git a/articles/backup/offline-backup-overview.md b/articles/backup/offline-backup-overview.md
@@ -0,0 +1,68 @@
+---
+title: Overview of Offline Backup 
+description: Learn about the various components of Offline Backup, including Azure Data Box based Offline Backup and Azure Import/Export based Offline Backup.
+ms.topic: conceptual
+ms.date: 1/28/2020
+---
+
+# Overview of Offline Backup
+
+This article gives an overview of Offline Backup.
+
+Initial full backups to Azure typically transfer large amounts of data online and require more network bandwidth when compared to subsequent backups that transfer only incremental changes. Remote offices or datacenters in certain geographies don't always have sufficient network bandwidth, so these initial backups may take several days. This ends up using the same network that was provisioned for applications running on the on-premises datacenter.
+
+Azure Backup supports "Offline Backup", which allows transferring initial backup data offline. It provides a mechanism to copy backup data onto physical storage-devices that are then shipped to a nearby Azure Datacenter and uploaded onto a Recovery Services Vault. This process ensures robust transfer of backup data without using any network bandwidth.
+
+## Offline Backup options
+
+Offline-Backup is offered in two modes based on the ownership of the storage devices.
+
+## Azure Data Box based Offline Backup (Preview)
+
+This mode is currently supported in only in preview. With the MARS Agent, this option takes advantage of the [Azure Data Box service](https://azure.microsoft.com/services/databox/) to ship Microsoft-proprietary, secure, and tamper-resistant transfer appliances with USB connectors, to your datacenter or remote office and writes backup data onto these devices. **This option saves the effort required to procure your own Azure compatible disks and connectors or provisioning temporary storage as a staging location.** In addition, Microsoft handles the end-to-end transfer logistics, which you can track through the Azure portal. An architecture describing the movement of backup data with this option is shown below.
+
+![Azure Backup Data Box architecture](./media/offline-backup-overview/azure-backup-databox-architecture.png)
+
+Here is a summary of the architecture:
+
+1. Azure Backup directly copies backup data to these pre-configured devices.
+2. You can then ship these devices back to an Azure Datacenter.
+3. The Azure Data Box service copies the data onto a customer-owned storage account.
+4. Azure Backup automatically copies backup data from the storage account to the designated Recovery Services Vault and incremental online backups are scheduled.
+
+To use Azure Data Box based Offline Backup, refer to [this article](offline-backup-azure-data-box.md).
+
+## Azure Import/Export based Offline Backup
+
+This option is supported by Azure Backup Server (MABS) / DPM-A / MARS Agent. It leverages the [Azure Import/Export service](https://docs.microsoft.com/azure/storage/common/storage-import-export-service) that enables you to transfer initial backup data to Azure by using your own Azure-compatible disks and connectors. This approach requires provisioning a temporary storage known as the **Staging Location** and usage of pre-built utilities to format and copy the backup data onto customer-owned disks. An architecture describing the movement of backup data with this option is shown below:
+
+![Azure Backup Import/Export architecture](./media/offline-backup-overview/azure-backup-import-export.png)
+
+Here is a summary of the architecture:
+
+1. Instead of sending the backup data over the network, Azure Backup writes the backup data to a staging location.
+2. The data in the staging location is written to one or more SATA disks using a custom utility.
+3. As part of the preparatory work, the utility creates an Azure Import job. The SATA drives are shipped to the nearest Azure datacenter, and reference the import job to connect the activities.
+4. At the Azure datacenter, the data on the disks is copied to an Azure storage account.
+5. Azure Backup copies the backup data from the storage account to the Recovery Services vault, and incremental backups are scheduled.
+
+To use Azure Import/Export based Offline Backup with the MARS Agent, refer to [this article](https://docs.microsoft.com/azure/backup/backup-azure-backup-import-export).
+
+To use the same along with MABS/DPM-A, refer to [this article](https://docs.microsoft.com/azure/backup/backup-azure-backup-server-import-export-).
+
+## Offline Backup Support Summary
+
+The table below compares the two available options so you can make the appropriate choices based on your scenario.
+
+| **Consideration**                                            | **Azure  Data Box Based offline Backup**                     | **Azure  Import/Export Based Offline Backup**                |
+| ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| Azure  Backup Deployment models                              | MARS  (Preview)                                              | MARS,  MABS, DPM-A                                           |
+| Maximum  Backup data per server (MARS) or per Protection Group (MABS, DPM-A) | Azure  Data Box Disk - 7.2 TB <br> Azure  Data Box - 80 TB       | 80  TB (up to 10 disks of 8 TB each)                          |
+| Security  (data, device & service)                           | [Data](https://docs.microsoft.com/azure/databox/data-box-security#data-box-data-protection) - AES-256 Bit  Encrypted <br> [Device](https://docs.microsoft.com/azure/databox/data-box-security#data-box-device-protection) - Rugged case,  proprietary credential-based interface to copy data <br> [Service](https://docs.microsoft.com/azure/databox/data-box-security#data-box-service-protection) - Protected by  Azure Security features | Data  - BitLocker Encrypted                                 |
+| Temporary  Staging Location provisioning                     | Not  required                                                | More  than or equal to the estimated backup data size        |
+| Supported  Regions                                           | [Azure Data Box   Disk regions](https://docs.microsoft.com/azure/databox/data-box-disk-overview#region-availability) <br> [Azure Data Box   regions](https://docs.microsoft.com/azure/databox/data-box-disk-overview#region-availability) | [IE regions](https://docs.microsoft.com/azure/storage/common/storage-import-export-service#region-availability) |
+| Cross-country  shipping*                                     | **Not  supported**  <br>    *Source  address & Destination Azure Datacenter must be in the same country* | Supported                                                    |
+| Transfer  Logistics (delivery, transport, pick-up)           | Fully  Microsoft managed                                     | Customer  managed                                            |
+| Pricing                                                      | [Azure Data Box   Pricing](https://azure.microsoft.com/pricing/details/databox/) <br> [Azure Data Box   Disk Pricing](https://azure.microsoft.com/pricing/details/databox/disk/) | [Azure   Import/Export Pricing](https://azure.microsoft.com/pricing/details/storage-import-export/) |
+
+*If your country doesn't have an Azure Datacenter, then you need to ship your disks to an Azure Datacenter in another country.
diff --git a/articles/backup/toc.yml b/articles/backup/toc.yml
@@ -252,10 +252,14 @@
       href: backup-azure-backup-cloud-as-tape.md
   - name: Offline backup
     items:
-     - name: Configure offline-backup
-       href: backup-azure-backup-import-export.md
-     - name: Offline backup for DPM and Azure Backup Server
-       href: backup-azure-backup-server-import-export-.md
+    - name: Overview
+      href: offline-backup-overview.md
+    - name: Offline Backup with Azure Data Box 
+      href: offline-backup-azure-data-box.md
+    - name: Offline Backup with Import/Export (MARS) 
+      href: backup-azure-backup-import-export.md
+    - name: Offline Backup with Import/Export (DPM/MABS)
+      href: backup-azure-backup-server-import-export-.md
   - name: Monitor and Alerts
     items:
     - name: Using the Azure portal

Original file line number	Diff line number	Diff line change
`@@ -328,4 +328,4 @@ From the server you are trying to configure offline backup, perform the followin`
`328`	`328`
`329`	`329`	`## Questions`
`330`	`330`
`331`		`-For any questions or clarifications, regarding any issues faced, reach out to [saurse@microsoft.com](mailto:saurse@microsoft.com)`
	`331`	`+For any questions or clarifications, regarding any issues faced, reach out to [AskAzureBackupTeam@microsoft.com](mailto:AskAzureBackupTeam@microsoft.com)`