Skip to content

Commit 981a1f9

Browse files
authored
Merge pull request #264304 from AbhishekMallick-MS/Jan-25-2024-Fresnhess
Freshness - Data recovery from MABS
2 parents 7872333 + fc18ec8 commit 981a1f9

File tree

3 files changed

+38
-14
lines changed

3 files changed

+38
-14
lines changed
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup
3+
description: Learn how to troubleshoot data recovery from Microsoft Azure Backup Server.
4+
ms.topic: troubleshooting
5+
ms.date: 01/26/2024
6+
ms.service: backup
7+
ms.custom: engagement-fy24
8+
author: AbhishekMallick-MS
9+
ms.author: v-abhmallick
10+
---
11+
12+
# Troubleshoot data recovery from Microsoft Azure Backup Server
13+
14+
This article provides troubleshooting steps that help you resolve error massages caused during data recovery from Microsoft Azure Backup Server.
15+
16+
## Troubleshoot error messages
17+
18+
| Error Message | Cause | Resolution |
19+
|:--- |:--- |:--- |
20+
|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. |
21+
|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. |
22+
|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. |
23+
|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. |
24+
25+
## Next steps
26+
27+
- [Common questions](backup-azure-vm-backup-faq.yml) about Azure VM backups.
28+
- [Common questions](backup-azure-file-folder-backup-faq.yml) about the Azure Backup agent.
29+
- [Recover data from Azure Backup Server](backup-azure-alternate-dpm-server.md).

articles/backup/backup-azure-alternate-dpm-server.md

Lines changed: 6 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Recover data from an Azure Backup Server
2+
title: Recover data from an Azure Backup Server by using Azure Backup
33
description: Recover the data you've protected to a Recovery Services vault from any Azure Backup Server registered to that vault.
44
ms.topic: how-to
5-
ms.date: 01/24/2023
5+
ms.date: 01/26/2024
66
ms.service: backup
7-
ms.custom: engagement-fy23
7+
ms.custom: engagement-fy24
88
author: AbhishekMallick-MS
99
ms.author: v-abhmallick
1010
---
@@ -75,18 +75,11 @@ To recover data from an Azure Backup Server, follow these steps:
7575

7676
![Screenshot shows how to clear external DPM.](./media/backup-azure-alternate-dpm-server/clear-external-dpm.png)
7777

78-
## Troubleshoot error messages
79-
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. |
8678

8779
## Next steps
8880

8981
Read the other FAQs:
9082

91-
* [Common questions](backup-azure-vm-backup-faq.yml) about Azure VM backups
92-
* [Common questions](backup-azure-file-folder-backup-faq.yml) about the Azure Backup agent
83+
- [Common questions](backup-azure-vm-backup-faq.yml) about Azure VM backups.
84+
- [Common questions](backup-azure-file-folder-backup-faq.yml) about the Azure Backup agent.
85+
- [Troubleshoot error messages](backup-azure-alternate-dpm-server-troubleshoot.md) caused during data recovery from Microsoft Azure Backup Server.

articles/backup/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -764,7 +764,9 @@
764764
- name: Archive tier
765765
href: troubleshoot-archive-tier.md
766766
- name: Azure Kubernetes Service
767-
href: azure-kubernetes-service-backup-troubleshoot.md
767+
href: azure-kubernetes-service-backup-troubleshoot.md
768+
- name: Data recovery from Microsoft Azure Backup Server
769+
href: backup-azure-alternate-dpm-server-troubleshoot.md
768770
- name: Reference
769771
items:
770772
- name: Archived release notes

0 commit comments

Comments
 (0)