Skip to content

Commit f105f32

Browse files
author
AbhishekMallick01
committed
Freshness - TSG data recovery from MABS
1 parent 15dc16d commit f105f32

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup
33
description: Learn how to troubleshoot data recovery from Microsoft Azure Backup Server.
44
ms.topic: troubleshooting
5-
ms.date: 01/26/2024
5+
ms.date: 01/31/2025
66
ms.service: azure-backup
77
ms.custom: engagement-fy24
88
author: jyothisuri
@@ -11,11 +11,12 @@ ms.author: jsuri
1111

1212
# Troubleshoot data recovery from Microsoft Azure Backup Server
1313

14-
This article provides troubleshooting steps that help you resolve error massages caused during data recovery from Microsoft Azure Backup Server.
14+
This article provides recommendations for troubleshooting common errors encountered during data recovery from Microsoft Azure Backup Server.
15+
1516

1617
## Troubleshoot error messages
1718

18-
| Error Message | Cause | Resolution |
19+
| Error Message | Cause | Recommendation |
1920
|:--- |:--- |:--- |
2021
|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. |
2122
|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. |

0 commit comments

Comments
 (0)