edit pass: backup-azure-backup-import-export

paulth1 · paulth1 · commit 919691240c4b · 2020-02-21T15:41:32.000-08:00
diff --git a/articles/backup/backup-azure-backup-import-export.md b/articles/backup/backup-azure-backup-import-export.md
@@ -27,26 +27,26 @@ The following Azure Backup features or workloads support the use of offline back
 
 > [!div class="checklist"]
 >
-> * Backup of files and folders with the Microsoft Azure Recovery Services (MARS) agent, also referred to as the Azure Backup agent.
+> * Backup of files and folders with the Microsoft Azure Recovery Services (MARS) Agent, also referred to as the Azure Backup Agent.
 > * Backup of all workloads and files with System Center Data Protection Manager (DPM).
 > * Backup of all workloads and files with Microsoft Azure Backup Server.
  
    > [!NOTE]
-   > Offline backup isn't supported for system state backups done by using the Azure Backup agent.
+   > Offline backup isn't supported for system state backups done by using the Azure Backup Agent.
 
 [!INCLUDE [backup-upgrade-mars-agent.md](../../includes/backup-upgrade-mars-agent.md)]
 
 ## Prerequisites
 
   > [!NOTE]
-  > The following prerequisites and workflow apply only to offline backup of files and folders using the [latest Azure Recovery Services agent](https://aka.ms/azurebackup_agent). To perform offline backups for workloads using System Center DPM or Azure Backup Server, see [Offline backup workflow for DPM and Azure Backup Server](backup-azure-backup-server-import-export-.md).
+  > The following prerequisites and workflow apply only to offline backup of files and folders using the [latest Azure Recovery Services Agent](https://aka.ms/azurebackup_agent). To perform offline backups for workloads using System Center DPM or Azure Backup Server, see [Offline backup workflow for DPM and Azure Backup Server](backup-azure-backup-server-import-export-.md).
 
 Before you start the offline backup workflow, complete the following prerequisites:
 
 * Create a [Recovery Services vault](backup-azure-recovery-services-vault-overview.md). To create a vault, follow the steps in [Create a Recovery Services vault](tutorial-backup-windows-server-to-azure.md#create-a-recovery-services-vault).
-* Make sure that only the [latest version of the Azure Backup agent](https://aka.ms/azurebackup_agent) is installed on the Windows Server or Windows client, as applicable, and the computer is registered with the Recovery Services vault.
-* Azure PowerShell 3.7.0 is required on the computer running the Azure Backup agent. Download and [install the 3.7.0 version of Azure PowerShell](https://github.com/Azure/azure-powershell/releases/tag/v3.7.0-March2017).
-* On the computer running the Azure Backup agent, make sure that Microsoft Edge or Internet Explorer 11 is installed and JavaScript is enabled.
+* Make sure that only the [latest version of the Azure Backup Agent](https://aka.ms/azurebackup_agent) is installed on the Windows Server or Windows client, as applicable, and the computer is registered with the Recovery Services vault.
+* Azure PowerShell 3.7.0 is required on the computer running the Azure Backup Agent. Download and [install the 3.7.0 version of Azure PowerShell](https://github.com/Azure/azure-powershell/releases/tag/v3.7.0-March2017).
+* On the computer running the Azure Backup Agent, make sure that Microsoft Edge or Internet Explorer 11 is installed and JavaScript is enabled.
 * Create an Azure storage account in the same subscription as the Recovery Services vault.
 * Make sure you have the [necessary permissions](../active-directory/develop/howto-create-service-principal-portal.md) to create the Azure Active Directory application. The offline backup workflow creates an Azure Active Directory application in the subscription associated with the Azure storage account. The goal of the application is to provide Azure Backup with secure and scoped access to the Azure Import/Export service, which is required for the offline backup workflow.
 * Register the *Microsoft.ImportExport* resource provider with the subscription that contains the Azure storage account. To register the resource provider:
@@ -59,22 +59,22 @@ Before you start the offline backup workflow, complete the following prerequisit
 
 * 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 want 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.)
 * When you send disks to Azure, use only 2.5-inch SSD or 2.5-inch or 3.5-inch SATA II/III internal hard drives. 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 must 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 Azure BitLocker is enabled on the copy computer.
+* The SATA drives must 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.
 
 ## Workflow
 
 This section describes 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 [Azure Import/Export service overview documentation](../storage/common/storage-import-export-service.md).
 
 ## Initiate offline backup
 
-1. When you schedule a backup on the Azure Recovery Services agent, you see this page.
+1. When you schedule a backup on the Recovery Services Agent, you see this page.
 
     ![Import page](./media/backup-azure-backup-import-export/offlinebackup_inputs.png)
 
 1. Select the option **Transfer using my own disks**.
 
     > [!NOTE]
-    > Use the Azure Data Box option to transfer initial backup data offline. This option saves the effort required to procure your own Azure-compatible disks. It delivers Microsoft-proprietary, secure, and tamperproof Azure Data Box devices to which backup data can be directly written to by the Azure Recovery Services agent.
+    > Use the Azure Data Box option to transfer initial backup data offline. This option saves the effort required to procure your own Azure-compatible disks. It delivers Microsoft-proprietary, secure, and tamperproof Azure Data Box devices to which backup data can be directly written to by the Recovery Services Agent.
 
 1. Select **Next**, and fill in the boxes carefully.
 
@@ -94,7 +94,7 @@ This section describes the offline backup workflow so that your data can be deli
 
     ![Azure subscription sign-in page](./media/backup-azure-backup-import-export/azure-login.png)
 
-1. Finish the workflow. On the Azure Backup agent console, select **Back Up Now**.
+1. Finish the workflow. On the Azure Backup Agent console, select **Back Up Now**.
 
     ![Back Up Now](./media/backup-azure-backup-import-export/backupnow.png)
 
@@ -108,7 +108,7 @@ This section describes the offline backup workflow so that your data can be deli
 
 ## Prepare SATA drives and ship to Azure
 
-The *AzureOfflineBackupDiskPrep* utility prepares the SATA drives that are sent to the nearest Azure datacenter. This utility is available in the Azure Backup agent installation directory in the following path:
+The *AzureOfflineBackupDiskPrep* utility prepares the SATA drives that are sent to the nearest Azure datacenter. This utility is available in the Azure Backup Agent installation directory in the following path:
 
     *\Microsoft Azure Recovery Services Agent\Utils\\*
 
diff --git a/articles/backup/backup-azure-backup-server-import-export-.md b/articles/backup/backup-azure-backup-server-import-export-.md
@@ -12,7 +12,7 @@ Azure Backup has several built-in efficiencies that save network and storage cos
 The offline-seeding process of Azure Backup is tightly integrated with the [Azure Import/Export service](../storage/common/storage-import-export-service.md). You can use this service to transfer data to Azure by using disks. If you have terabytes (TBs) of initial backup data that need to be transferred over a high-latency and low-bandwidth network, you can use the offline-seeding workflow to ship the initial backup copy on one or more hard drives to an Azure datacenter. This article provides an overview and further steps that finish this workflow for System Center Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS).
 
 > [!NOTE]
-> The process of offline backup for the Microsoft Azure Recovery Services (MARS) agent is distinct from DPM and MABS. For information on using offline backup with the MARS agent, see [Offline backup workflow in Azure Backup](backup-azure-backup-import-export.md). Offline backup isn't supported for system state backups done by using the Azure Backup agent.
+> The process of offline backup for the Microsoft Azure Recovery Services (MARS) Agent is distinct from DPM and MABS. For information on using offline backup with the MARS Agent, see [Offline backup workflow in Azure Backup](backup-azure-backup-import-export.md). Offline backup isn't supported for system state backups done by using the Azure Backup Agent.
 >
 
 ## Overview
@@ -33,7 +33,7 @@ Offline backup is supported for all deployment models of Azure Backup that back
 
 > [!div class="checklist"]
 >
-> * Backup of files and folders with the MARS agent or the Azure Backup agent.
+> * Backup of files and folders with the MARS Agent or the Azure Backup Agent.
 > * Backup of all workloads and files with DPM.
 > * Backup of all workloads and files with MABS.
 
@@ -42,7 +42,7 @@ Offline backup is supported for all deployment models of Azure Backup that back
 Ensure that the following prerequisites are met before you start the offline backup workflow:
 
 * A [Recovery Services vault](backup-azure-recovery-services-vault-overview.md) has been created. To create one, follow the steps in [Create a Recovery Services vault](tutorial-backup-windows-server-to-azure.md#create-a-recovery-services-vault)
-* An Azure Backup agent or MABS or DPM has been installed on either Windows Server or a Windows client, as applicable, and the computer is registered with the Recovery Services vault. Ensure that only the [latest version of Azure Backup](https://go.microsoft.com/fwlink/?linkid=229525) is used.
+* An Azure Backup Agent or MABS or DPM has been installed on either Windows Server or a Windows client, as applicable, and the computer is registered with the Recovery Services vault. Ensure that only the [latest version of Azure Backup](https://go.microsoft.com/fwlink/?linkid=229525) is used.
 * [Download the Azure publish settings file](https://portal.azure.com/#blade/Microsoft_Azure_ClassicResources/PublishingProfileBlade) on the computer from which you plan to back up your data. The subscription from which you download the publish settings file can be different from the subscription that contains the Recovery Services vault. If your subscription is on sovereign Azure clouds, then use the following links as appropriate to download the Azure publish settings file.
 
     | Sovereign cloud region | Azure publish settings file link |
@@ -56,12 +56,12 @@ Ensure that the following prerequisites are met before you start the offline bac
 
 * 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 want 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.)
 * For disks 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 must 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 Azure BitLocker is enabled on the copy computer.
+* The SATA drives must 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 can't 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.
+> If you can't 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:
 
@@ -74,7 +74,7 @@ Ensure that the following prerequisites are met before you start the offline bac
     If an application already exists, this executable asks you to manually upload the certificate to the application in the tenant. Follow the steps in [this section](#manually-upload-an-offline-backup-certificate) to upload the certificate manually to the application.
 
 * The *AzureOfflineBackup.exe* tool generates 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 instance or the Azure Backup server.
+* Install the [latest MARS Agent](https://aka.ms/azurebackup_agent) on the DPM instance or the Azure Backup server.
 * Register the server to Azure.
 * Run the following command:
 
@@ -145,7 +145,7 @@ The information in this section helps you finish the offline backup workflow so
 
    Save the **Staging Location** and the **Azure Import Job Name** information you provided. It's required to prepare the disks.
 
-1. Finish the workflow. To initiate the offline backup copy, select **Back Up Now** on the Azure Backup agent management console. The initial backup is written to the staging area as part of this step.
+1. Finish the workflow. To initiate the offline backup copy, select **Back Up Now** on the Azure Backup Agent management console. The initial backup is written to the staging area as part of this step.
 
     ![Backup now](./media/backup-azure-backup-import-export/backupnow.png)
 
@@ -159,7 +159,7 @@ The information in this section helps you finish the offline backup workflow so
 
 ### Prepare SATA drives and ship to Azure
 
-The *AzureOfflineBackupDiskPrep* utility is used to prepare the SATA drives that are sent to the nearest Azure datacenter. This utility is available in the installation directory of the Recovery Services agent in the following path:
+The *AzureOfflineBackupDiskPrep* utility is used to prepare the SATA drives that are sent to the nearest Azure datacenter. This utility is available in the installation directory of the Recovery Services Agent in the following path:
 
 `*\\Microsoft Azure Recovery Services Agent\Utils\*`
 
@@ -246,7 +246,7 @@ The amount of time it takes to process an Azure import job varies. The process t
 
 ### Monitor Azure import job status
 
-While your drives are in transit or at the Azure datacenter to be copied to the storage account, the Azure Backup agent or DPM or the MABS console on the source computer shows the following job status for your scheduled backups:
+While your drives are in transit or at the Azure datacenter to be copied to the storage account, the Azure Backup Agent or DPM or the MABS console on the source computer shows the following job status for your scheduled backups:
 
   `Waiting for Azure Import Job to complete. Please check on Azure Management portal for more information on job status`
 
diff --git a/includes/backup-upgrade-mars-agent.md b/includes/backup-upgrade-mars-agent.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrade the Azure Backup agent
-description: This information explains why you should upgrade the Azure Backup agent, and where to download the upgrade.
+title: Upgrade the Azure Backup Agent
+description: This information explains why you should upgrade the Azure Backup Agent, and where to download the upgrade.
 services: backup
 cloud: 
 suite: 
@@ -15,10 +15,10 @@ ms.date: 8/29/2018
 ms.author: dacurwin
 ---
 
-## Upgrade the MARS agent
+## Upgrade the MARS Agent
 
-Versions of the Microsoft Azure Recovery Services (MARS) agent below 2.0.9083.0 have a dependency on the Azure Access Control service. The MARS agent is also referred to as the Azure Backup agent.
+Versions of the Microsoft Azure Recovery Services (MARS) Agent below 2.0.9083.0 have a dependency on the Azure Access Control service. The MARS Agent is also referred to as the Azure Backup Agent.
 
-In 2018, Microsoft [deprecated the Azure Access Control service](../articles/active-directory/azuread-dev/active-directory-acs-migration.md). Beginning March 19, 2018, all versions of the MARS agent below 2.0.9083.0 will experience backup failures. To avoid or resolve backup failures, [upgrade your MARS agent to the latest version](https://go.microsoft.com/fwlink/?linkid=229525). To identify servers that require a MARS agent upgrade, follow the steps in the [Backup blog for upgrading MARS agents](https://blogs.technet.microsoft.com/srinathv/2018/01/17/updating-azure-backup-agents/).
+In 2018, Microsoft [deprecated the Azure Access Control service](../articles/active-directory/azuread-dev/active-directory-acs-migration.md). Beginning March 19, 2018, all versions of the MARS Agent below 2.0.9083.0 will experience backup failures. To avoid or resolve backup failures, [upgrade your MARS Agent to the latest version](https://go.microsoft.com/fwlink/?linkid=229525). To identify servers that require a MARS Agent upgrade, follow the steps in the [Backup blog for upgrading MARS Agents](https://blogs.technet.microsoft.com/srinathv/2018/01/17/updating-azure-backup-agents/).
 
-The MARS agent is used to back up files and folders and system state data to Azure. System Center DPM and Azure Backup Server use the MARS agent to back up data to Azure.
+The MARS Agent is used to back up files and folders and system state data to Azure. System Center DPM and Azure Backup Server use the MARS Agent to back up data to Azure.
