Skip to content

Commit 25e2c2b

Browse files
author
AbhishekMallick01
committed
Freshness - SC DPM TSG
1 parent f105f32 commit 25e2c2b

File tree

1 file changed

+17
-9
lines changed

1 file changed

+17
-9
lines changed

articles/backup/backup-azure-scdpm-troubleshooting.md

Lines changed: 17 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Troubleshoot System Center Data Protection Manager
33
description: In this article, discover solutions for issues that you might encounter while using System Center Data Protection Manager.
44
ms.topic: troubleshooting
5-
ms.date: 10/21/2022
5+
ms.date: 01/31/2025
66
ms.service: azure-backup
77
author: jyothisuri
88
ms.author: jsuri
@@ -14,7 +14,11 @@ This article describes solutions for issues that you might encounter while using
1414

1515
For the latest release notes for System Center Data Protection Manager, see the [System Center documentation](/system-center/dpm/dpm-release-notes). You can learn more about support for Data Protection Manager in [this matrix](/system-center/dpm/dpm-protection-matrix).
1616

17-
## Error: Replica is inconsistent
17+
## Common errors
18+
19+
This section lists the common errors and the recommended actions to resolve them.
20+
21+
### Error: Replica is inconsistent
1822

1923
A replica can be inconsistent for the following reasons:
2024

@@ -36,7 +40,7 @@ To resolve this issue, perform the following actions:
3640
- Ensure that the disk is healthy and that there's enough space for the replica.
3741
- Ensure that there are no duplicate backup jobs that are running concurrently.
3842

39-
## Error: Online recovery point creation failed
43+
### Error: Online recovery point creation failed
4044

4145
To resolve this issue, perform the following actions:
4246

@@ -48,7 +52,7 @@ To resolve this issue, perform the following actions:
4852
- Ensure that the replica is present and not missing.
4953
- Ensure that the replica has sufficient space to create the update sequence number (USN) journal.
5054

51-
## Error: Unable to configure protection
55+
### Error: Unable to configure protection
5256

5357
This error occurs when the Data Protection Manager server can't contact the protected server.
5458

@@ -58,7 +62,7 @@ To resolve this issue, perform the following actions:
5862
- Ensure that there's connectivity (network/firewall/proxy) between your Data Protection Manager server and the protected server.
5963
- If you're protecting a SQL server, ensure that the **Login Properties** > **NT AUTHORITY\SYSTEM** property shows the **sysadmin** setting enabled.
6064

61-
## Error: Server not registered as specified in vault credential file
65+
### Error: Server not registered as specified in vault credential file
6266

6367
This error occurs during the recovery process for Data Protection Manager/Azure Backup server data. The vault credential file that's used in the recovery process doesn't belong to the Recovery Services vault for the Data Protection Manager/Azure Backup server.
6468

@@ -67,7 +71,7 @@ To resolve this issue, perform these steps:
6771
1. Download the vault credential file from the Recovery Services vault to which the Data Protection Manager/Azure Backup server is registered.
6872
2. Try to register the server with the vault by using the most recently downloaded vault credential file.
6973

70-
## Error: No recoverable data or selected server not a Data Protection Manager server
74+
### Error: No recoverable data or selected server not a Data Protection Manager server
7175

7276
This error occurs for the following reasons:
7377

@@ -80,7 +84,7 @@ When other Data Protection Manager/Azure Backup servers are registered to the Re
8084
1. Ensure that the latest Azure Backup agent is installed.
8185
2. After you ensure that the latest agent is installed, wait one day before you start the recovery process. The nightly backup job uploads the metadata for all of the protected backups to the cloud. The backup data is then available for recovery.
8286

83-
## Error: Provided encryption passphrase doesn't match passphrase for server
87+
### Error: Provided encryption passphrase doesn't match passphrase for server
8488

8589
This error occurs during the encryption process when recovering Data Protection Manager/Azure Backup server data. The encryption passphrase that's used in the recovery process doesn't match the server's encryption passphrase. As a result, the agent can't decrypt the data and the recovery fails.
8690

@@ -90,10 +94,14 @@ This error occurs during the encryption process when recovering Data Protection
9094
> When you're recovering data, always provide the same encryption passphrase that's associated with the Data Protection Manager/Azure Backup server.
9195
>
9296
93-
## Error: The server registration status could not be verified with Microsoft Azure Backup. Verify that you are connected to the internet and that the proxy settings are configured correctly.
97+
### Error: The server registration status could not be verified with Microsoft Azure Backup. Verify that you are connected to the internet and that the proxy settings are configured correctly.
9498

9599
To resolve this issue:
96100

97101
- Ensure network connectivity and proxy settings.
98102
- Ensure that you are running the latest MARS agent.
99-
- [Ensure your server is running on TLS 1.2](transport-layer-security.md).
103+
- [Ensure your server is running on TLS 1.2](transport-layer-security.md).
104+
105+
## Next step
106+
107+
[Prepare to back up workloads to Azure with System Center DPM](backup-azure-dpm-introduction.md)

0 commit comments

Comments
 (0)