You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/offline-backup-server-previous-versions.md
+37-33Lines changed: 37 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,23 +1,29 @@
1
1
---
2
2
title: Offline backup for Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS) - previous versions
3
3
description: With Azure Backup, you can send data off the network by using the Azure Import/Export service. This article explains the offline backup workflow for previous versions of DPM and Azure Backup Server.
4
-
ms.topic: conceptual
5
-
ms.date: 06/08/2020
4
+
ms.topic: how-to
5
+
ms.date: 01/23/2023
6
+
author: jyothisuri
7
+
ms.author: jsuri
8
+
ms.service: backup
9
+
ms.custom: engagement-fy23
6
10
---
7
11
# Offline backup workflow for DPM and Azure Backup Server (previous versions)
8
12
13
+
This article describes about offline backup and how to finish this workflow for System Center Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS).
14
+
9
15
>[!IMPORTANT]
10
16
>These steps are applicable for DPM 2019 RTM and earlier versions and MABS v3 RTM and earlier versions.
11
17
12
18
Azure Backup has several built-in efficiencies that save network and storage costs during the initial full backups of data to Azure. Initial full backups typically transfer large amounts of data and require more network bandwidth when compared to subsequent backups that transfer only the deltas/incrementals. 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.
13
19
14
-
The offline-seeding process of Azure Backup is tightly integrated with the [Azure Import/Export service](../import-export/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).
20
+
The offline-seeding process of Azure Backup is tightly integrated with the [Azure Import/Export service](../import-export/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.
15
21
16
22
> [!NOTE]
17
23
> 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.
18
24
>
19
25
20
-
## Overview
26
+
## Offline backup process
21
27
22
28
With the offline-seeding capability of Azure Backup and the Azure Import/Export service, it's simple to upload the data offline to Azure by using disks. The offline backup process involves the following steps:
23
29
@@ -33,11 +39,9 @@ With the offline-seeding capability of Azure Backup and the Azure Import/Export
33
39
34
40
Offline backup is supported for all deployment models of Azure Backup that back up data from on-premises to the Microsoft cloud. These models include:
35
41
36
-
> [!div class="checklist"]
37
-
>
38
-
> * Backup of files and folders with the MARS Agent or the Azure Backup Agent.
39
-
> * Backup of all workloads and files with DPM.
40
-
> * Backup of all workloads and files with MABS.
42
+
- Backup of files and folders with the MARS Agent or the Azure Backup Agent.
43
+
- Backup of all workloads and files with DPM.
44
+
- Backup of all workloads and files with MABS.
41
45
42
46
>[!NOTE]
43
47
>Azure CSP subscriptions aren't supported for use with offline seeding for DPM 2019 RTM and earlier versions, and MABS v3 RTM and earlier versions. Online backups over the network are still supported.
@@ -57,7 +61,7 @@ Ensure that the following prerequisites are met before you start the offline bac
57
61
58
62
* An Azure storage account with the Resource Manager deployment model has been created in the subscription from which you downloaded the publish settings file. In the storage account, create a new blob container, which will be used as the destination.
59
63
60
-

64
+

61
65
62
66
* 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.)
63
67
* 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](../import-export/storage-import-export-requirements.md#supported-hardware) for the latest set of drives that the service supports.
@@ -76,7 +80,7 @@ Ensure that the following prerequisites are met before you start the offline bac
76
80
77
81
The tool creates an Azure Offline Backup Active Directory Application if one doesn't exist.
78
82
79
-
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.
83
+
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](#upload-an-offline-backup-certificate-manually) to upload the certificate manually to the application.
80
84
81
85
* The *AzureOfflineBackupCertGen.exe* tool generates an *OfflineApplicationParams.xml* file. Copy this file to the server with MABS or DPM.
82
86
* Install the [latest MARS Agent](https://aka.ms/azurebackup_agent) on the DPM instance or the Azure Backup server.
@@ -89,24 +93,24 @@ Ensure that the following prerequisites are met before you start the offline bac
89
93
90
94
* The previous command creates the file `C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch\MicrosoftBackupProvider\OfflineApplicationParams_<Storageaccountname>.xml`.
91
95
92
-
## Manually upload an offline backup certificate
96
+
## Upload an offline backup certificate manually
93
97
94
-
Follow these steps to manually upload the offline backup certificate to a previously created Azure Active Directory application meant for offline backup.
98
+
To manually upload the offline backup certificate to a previously created Azure Active Directory application meant for offline backup, follow these steps:
95
99
96
100
1. Sign in to the Azure portal.
97
101
1. Go to **Azure Active Directory** > **App registrations**.
98
102
1. On the **Owned applications** tab, locate an application with the display name format `AzureOfflineBackup _<Azure User Id`.
99
103
100
-

104
+

101
105
102
106
1. Select the application. Under **Manage** on the left pane, go to **Certificates & secrets**.
103
-
1. Check for pre-existing certificates or public keys. If there are none, you can safely delete the application by selecting the **Delete** button on the application's **Overview** page. Then you can retry the steps to [prepare the server for the offline backup](#prepare-the-server-for-the-offline-backup-process) process, and skip the following steps. Otherwise, continue to follow these steps from the DPM instance or Azure Backup server where you want to configure offline backup.
107
+
1. Check for pre-existing certificates or public keys. If there's none, you can safely delete the application by selecting the **Delete** button on the application's **Overview** page. Then you can retry the steps to [prepare the server for the offline backup](#prepare-the-server-for-the-offline-backup-process) process, and skip the following steps. Otherwise, continue to follow these steps from the DPM instance or Azure Backup server where you want to configure offline backup.
104
108
1. From **Start** – **Run**, type *Certlm.msc*. In the **Certificates - Local Computer** window, select the **Certificates – Local Computer** > **Personal** tab. Look for the certificate with the name `CB_AzureADCertforOfflineSeeding_<ResourceId>`.
105
109
1. Select the certificate, right-click **All Tasks**, and then select **Export**, without a private key, in the .cer format.
106
110
1. Go to the Azure offline backup application in the Azure portal.
107
111
1. Select **Manage** > **Certificates & secrets** > **Upload certificate**. Upload the certificate exported in the previous step.
108
112
109
-

113
+

110
114
111
115
1. On the server, open the registry by entering **regedit** in the run window.
112
116
1. Go to the registry entry *Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config\CloudBackupProvider*.
@@ -121,23 +125,23 @@ Follow these steps to manually upload the offline backup certificate to a previo
121
125
1. Right-click the string added in the previous step, and select **Modify**. In the value, provide the thumbprint of the certificate you exported in step 7. Then select **OK**.
122
126
1. To get the value of the thumbprint, double-click the certificate. Select the **Details** tab, and scroll down until you see the thumbprint field. Select **Thumbprint**, and copy the value.
123
127
124
-

128
+

125
129
126
-
1. Continue to the [Workflow](#workflow) section to proceed with the offline backup process.
130
+
1. Continue to the [Finish the offline workflow](#finish-the-offline-backup-workflow) section to proceed with the offline backup process.
127
131
128
-
## Workflow
132
+
## Finish the offline backup workflow
129
133
130
134
The information in this section helps you finish 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 documentation](../import-export/storage-import-export-service.md) referenced earlier.
131
135
132
136
### Initiate offline backup
133
137
134
138
1. When you schedule a backup, you see the following page in Windows Server, a Windows client, or DPM.

137
141
138
142
Here's the corresponding page in DPM. <br/>
139
143
140
-

144
+

141
145
142
146
The boxes that you fill in are:
143
147
@@ -152,15 +156,15 @@ The information in this section helps you finish the offline backup workflow so
152
156
153
157
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.

156
160
157
-
To finish the corresponding workflow in DPM or Azure Backup Server, right-click the **Protection Group**. Select the **Create recovery point** option. Then select the **Online Protection** option.
161
+
To finish the corresponding workflow in DPM or Azure Backup Server, right-click the **Protection Group**, and then select **Create recovery point** > **Online Protection**.
158
162
159
-

163
+

160
164
161
165
After the operation finishes, the staging location is ready to be used for disk preparation.

164
168
165
169
### Prepare SATA drives and ship to Azure
166
170
@@ -193,19 +197,19 @@ The *AzureOfflineBackupDiskPrep* utility is used to prepare the SATA drives that
193
197
194
198
When you run the command, the utility requests the selection of the Azure import job that corresponds to the drives that need to be prepared. If only a single import job is associated with the provided staging location, you see a page like this one.
195
199
196
-
 <br/>
200
+
 <br/>
197
201
198
202
1. Enter the drive letter without the trailing colon for the mounted disk that you want to prepare for transfer to Azure. When prompted, provide confirmation for the formatting of the drive.
199
203
200
204
The tool then begins to prepare the disk and copy the backup data. You might need to attach additional disks when prompted by the tool if the provided disk doesn't have sufficient space for the backup data. <br/>
201
205
202
206
After the tool finishes successfully, one or more disks that you provided are prepared for shipping to Azure. An import job with the name you provided during the workflow in the "Initiate offline backup" section also is created in Azure. Finally, the tool displays the shipping address to the Azure datacenter where the disks need to be shipped.
203
207
204
-
<br/>
208
+
<br/>
205
209
206
210
1. At the end of the command execution, you also see the option to update shipping information.
207
211
208
-
<br/>
212
+
<br/>
209
213
210
214
1. You can enter the details right away. The tool guides you through the process that involves a series of inputs. If you don't have information like the tracking number or other details related to shipping, you can end the session. The steps to update shipping details later are provided in this article.
211
215
@@ -230,15 +234,15 @@ The *AzureOfflineBackupDiskPrep* utility is used to prepare the SATA drives that
230
234
231
235
The utility automatically detects the import job that the source computer is waiting on or the import jobs associated with the staging location when the command is run on a different computer. It then provides the option to update shipping information through a series of inputs.
<br/>
242
246
243
247
> [!IMPORTANT]
244
248
> Ensure that the drives reach the Azure datacenter within two weeks of providing the shipping information by using the *AzureOfflineBackupDiskPrep* utility. Failure to do so can result in the drives not being processed.
@@ -263,15 +267,15 @@ To check the import job status:
263
267
264
268
1. The output shows the current status of the import job.
<br/>
267
271
268
272
For more information on the various states of the Azure import job, see [View the status of Azure Import/Export jobs](../import-export/storage-import-export-view-drive-status.md).
269
273
270
274
### Finish the workflow
271
275
272
276
After the import job finishes, initial backup data is available in your storage account. At the time of the next scheduled backup, Azure Backup copies the contents of the data from the storage account to the Recovery Services vault.
273
277
274
-
<br/>
278
+
<br/>
275
279
276
280
At the time of the next scheduled backup, Azure Backup performs incremental backup over the initial backup copy.
0 commit comments