Skip to content

Commit f7b7be5

Browse files
committed
edit pass: backup-azure-backup-import-export
1 parent fdf6214 commit f7b7be5

File tree

3 files changed

+8
-4
lines changed

3 files changed

+8
-4
lines changed

articles/backup/backup-azure-backup-import-export.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ The Azure Backup offline-seeding process is tightly integrated with the [Azure I
1313

1414
![Overview of offline import workflow process](./media/backup-azure-backup-import-export/offlinebackupworkflowoverview.png)
1515

16-
The offline backup process involves the following steps:
16+
The offline backup process involves these steps:
1717

1818
1. Instead of sending the backup data over the network, write the backup data to a staging location.
1919
1. Use the *AzureOfflineBackupDiskPrep* utility to write the data in the staging location to one or more SATA disks.
@@ -112,7 +112,7 @@ The *AzureOfflineBackupDiskPrep* utility prepares the SATA drives that are sent
112112

113113
*\Microsoft Azure Recovery Services Agent\Utils\\*
114114

115-
1. Go to the directory, and copy the **AzureOfflineBackupDiskPrep** directory to another computer where the SATA drives are connected. On the computer with the connected SATA drives, ensure that:
115+
1. Go to the directory, and copy the *AzureOfflineBackupDiskPrep* directory to another computer where the SATA drives are connected. On the computer with the connected SATA drives, ensure that:
116116

117117
* The copy computer can access the staging location for the offline-seeding workflow by using the same network path that was provided in the workflow in the "Initiate offline backup" section.
118118
* BitLocker is enabled on the copy computer.

articles/backup/backup-azure-backup-server-import-export-.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ The information in this section helps you finish the offline backup workflow so
143143
* **Azure Storage Account**: The name of the storage account in the Azure subscription associated with the Azure publish settings file.
144144
* **Azure Storage Container**: The name of the destination storage blob in the Azure storage account where the backup data is imported.
145145
146-
Save the **Staging Location** and the **Azure Import Job Name** information you provided. It's required to prepare the disks.
146+
Save the **Staging Location** and the **Azure Import Job Name** information you provided. It's required to prepare the disks.
147147
148148
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.
149149

includes/backup-upgrade-mars-agent.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,8 @@ ms.author: dacurwin
1717

1818
## Upgrade the MARS agent
1919

20-
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/). 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.
20+
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.
21+
22+
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/).
23+
24+
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.

0 commit comments

Comments
 (0)