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/backup-azure-alternate-dpm-server.md
+34-29Lines changed: 34 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,50 +1,56 @@
1
1
---
2
2
title: Recover data from an Azure Backup Server
3
3
description: Recover the data you've protected to a Recovery Services vault from any Azure Backup Server registered to that vault.
4
-
ms.topic: conceptual
5
-
ms.date: 07/09/2019
4
+
ms.topic: how-to
5
+
ms.date: 01/24/2023
6
+
author: jyothisuri
7
+
ms.author: jsuri
8
+
ms.service: backup
9
+
ms.custom: engagement-fy23
6
10
---
11
+
7
12
# Recover data from Azure Backup Server
8
13
9
-
You can use Azure Backup Server to recover the data you've backed up to a Recovery Services vault. The process for doing so is integrated into the Azure Backup Server management console, and is similar to the recovery workflow for other Azure Backup components.
14
+
This article describes how to recover data from Azure Backup Server.
15
+
16
+
You can use Azure Backup Server to recover the data you've backed-up to a Recovery Services vault. The process for doing so is integrated into the Azure Backup Server management console, and is similar to the recovery workflow for other Azure Backup components.
10
17
11
18
> [!NOTE]
12
19
> This article is applicable for [System Center Data Protection Manager 2012 R2 with UR7 or later](https://support.microsoft.com/kb/3065246), combined with the [latest Azure Backup agent](https://aka.ms/azurebackup_agent).
13
-
>
14
-
>
15
20
16
-
To recover data from an Azure Backup Server:
21
+
## Recover the data
22
+
23
+
To recover data from an Azure Backup Server, follow these steps:
17
24
18
-
1.From the **Recovery** tab of the Azure Backup Server management console, select **'Add External DPM'** (at the top left of the screen).
25
+
1.On the **Recovery** tab of the Azure Backup Server management console, select **'Add External DPM'** (at the top left of the screen).
21
28
2. Download new **vault credentials** from the vault associated with the **Azure Backup Server** where the data is being recovered, choose the Azure Backup Server from the list of Azure Backup Servers registered with the Recovery Services vault, and provide the **encryption passphrase** associated with the server whose data is being recovered.
24
31
25
32
> [!NOTE]
26
33
> Only Azure Backup Servers associated with the same registration vault can recover each other’s data.
27
-
>
28
-
>
34
+
29
35
30
36
Once the External Azure Backup Server is successfully added, you can browse the data of the external server and the local Azure Backup Server from the **Recovery** tab.
31
37
3. Browse the available list of production servers protected by the external Azure Backup Server and select the appropriate data source.
34
40
4. Select **the month and year** from the **Recovery points** drop down, select the required **Recovery date** for when the recovery point was created, and select the **Recovery time**.
35
41
36
42
A list of files and folders appears in the bottom pane, which can be browsed and recovered to any location.
37
43
38
-
44
+
39
45
5. Right-click the appropriate item and select **Recover**.
42
48
6. Review the **Recover Selection**. Verify the data and time of the backup copy being recovered, as well as the source from which the backup copy was created. If the selection is incorrect, select **Cancel** to navigate back to recovery tab to select appropriate recovery point. If the selection is correct, select **Next**.
48
54
8. Choose the option related to **create copy**, **Skip**, or **Overwrite**.
49
55
50
56
***Create copy** - creates a copy of the file if there's a name collision.
@@ -55,29 +61,28 @@ To recover data from an Azure Backup Server:
55
61
56
62
Identify whether a **Notification** is sent, once the recovery successfully completes.
59
65
9. The **Summary** screen lists the options chosen so far. Once you select **Recover**, the data is recovered to the appropriate on-premises location.
62
68
63
69
> [!NOTE]
64
70
> The recovery job can be monitored in the **Monitoring** tab of the Azure Backup Server.
72
77
73
-
## Troubleshooting error messages
78
+
## Troubleshoot error messages
74
79
75
-
|No. |Error Message |Troubleshooting steps|
76
-
|:---:|:--- |:--- |
77
-
| 1. |This server is not registered to the vault specified by the vault credential. |**Cause:** This error appears when the vault credential file selected does not belong to the Recovery Services vault associated with Azure Backup Server on which the recovery is attempted. <br> **Resolution:** Download the vault credential file from the Recovery Services vault to which the Azure Backup Server is registered. |
78
-
| 2. |Either the recoverable data is not available or the selected server is not a DPM server. |**Cause:** There are no other Azure Backup Servers registered to the Recovery Services vault, or the servers have not yet uploaded the metadata, or the selected server is not an Azure Backup Server (using Windows Server or Windows Client). <br> **Resolution:** If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed. <br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job will upload the metadata for all the protected backups to cloud. The data will be available for recovery. |
79
-
| 3. |No other DPM server is registered to this vault. |**Cause:** There are no other Azure Backup Servers that are registered to the vault from which the recovery is being attempted.<br>**Resolution:** If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed.<br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job uploads the metadata for all protected backups to cloud. The data will be available for recovery. |
80
-
| 4. |The encryption passphrase provided does not match with passphrase associated with the following server: **\<server name>**|**Cause:** The encryption passphrase used in the process of encrypting the data from the Azure Backup Server’s data that's being recovered doesn't match the encryption passphrase provided. The agent is unable to decrypt the data, and so the recovery fails.<br>**Resolution:** Provide the exact same encryption passphrase associated with the Azure Backup Server whose data is being recovered. |
80
+
| Error Message |Cause | Resolution|
81
+
|:---|:--- |:--- |
82
+
|This server is not registered to the vault specified by the vault credential. | This error appears when the vault credential file selected doesn't belong to the Recovery Services vault associated with Azure Backup Server on which the recovery is attempted. | Download the vault credential file from the Recovery Services vault to which the Azure Backup Server is registered. |
83
+
|Either the recoverable data isn't available or the selected server isn't a DPM server. | There are no other Azure Backup Servers registered to the Recovery Services vault, or the servers haven't yet uploaded the metadata, or the selected server isn't an Azure Backup Server (using Windows Server or Windows Client). | If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed. <br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job will upload the metadata for all the protected backups to cloud. The data will be available for recovery. |
84
+
|No other DPM server is registered to this vault. | There are no other Azure Backup Servers that are registered to the vault from which the recovery is being attempted.| If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed.<br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job uploads the metadata for all protected backups to cloud. The data will be available for recovery. |
85
+
|The encryption passphrase provided does not match with passphrase associated with the following server: **\<server name>**| The encryption passphrase used in the process of encrypting the data from the Azure Backup Server’s data that's being recovered doesn't match the encryption passphrase provided. The agent is unable to decrypt the data, and so the recovery fails.| Provide the exact same encryption passphrase associated with the Azure Backup Server whose data is being recovered. |
0 commit comments