DPM 2022 - Consistency Check stuck with "Replica is inconsistent" for all Domain Controllers

Question

Hello Support Team,

We are experiencing an issue with Microsoft System Center Data Protection Manager (DPM) 2022 in our production environment.

• Environment
• DPM Version: 10.22.123.0
• DPM Server OS: Windows Server 2022
• SQL Instance: SQL Server (MSSQLSERVER)
• Issue Description
  All Domain Controllers have the same issue.

The following data sources are affected:

• C: volume
• SYSVOL
• NETLOGON

Current status:

• Replica is inconsistent
• Verification in progress

The Consistency Check job remains in progress for a very long time and never completes.

From the Job Details:

• Data transferred: 0 MB
• Items scanned: 0
• Items fixed: 0

The job remains running for more than 43 hours (some jobs have been repeating for several days).All Domain Controllers have the same issue.

The following data sources are affected:

• C: volume
• SYSVOL
• NETLOGON

Current status:

• Replica is inconsistent
• Verification in progress

The Consistency Check job remains in progress for a very long time and never completes.

From the Job Details:

• Data transferred: 0 MB
• Items scanned: 0
• Items fixed: 0

The job remains running for more than 43 hours (some jobs have been repeating for several days).

• What's Working
  The following backups are still completing successfully for all Domain Controllers:
• Bare Metal Recovery
• System State

Only the following workloads are affected:

• C:
• SYSVOL
• NETLOGON The following backups are still completing successfully for all Domain Controllers:
  • Bare Metal Recovery
  • System State
  Only the following workloads are affected:
  • C:
  • SYSVOL
  • NETLOGON

Answer 1

Hi Duc,

Based on your description, the fact that Bare Metal Recovery and System State backups continue to succeed while only the C:, SYSVOL, and NETLOGON replicas remain in "Replica is inconsistent" with the Consistency Check stuck at 0 MB transferred, 0 items scanned, and 0 items fixed suggests this is not a general connectivity issue between the DPM server and the protected Domain Controllers. However, the information provided is not sufficient to determine whether the root cause is related to the DPM replica, VSS, DPMRA, storage, SQL metadata, or a known product issue.

As a first step, please review the DPM and Application event logs on both the DPM server and the affected Domain Controllers, verify that all DPM 2022 updates are installed, and collect the DPM diagnostic logs using DPMCBT, DPMRACurr.errlog, and the DPM Diagnostic Tool if available. These logs are required to identify why the consistency check never progresses.

Since this issue requires detailed log analysis and may involve the DPM engine itself, I recommend opening a Microsoft Unified or Premier Support request, if available. The support engineer can analyze the DPM logs, SQL database state, and replica metadata to determine the underlying cause and recommend the appropriate supported remediation.