Systems Center DPM 2022 UR2 - Errors protecting Hyper-V Hosts

Jeff Poblocki 21 Reputation points

I recently installed UR2 for Systems Center DPM 2022. I have 2 Hyper-V hosts running Windows Server 2022. Whenever a Recovery Point is created (either Scheduled or Manually) it immediately fails, with Error ID 30135 stating the Replica is Inconsistent. I can run a manual Consistency Check and it completes successfully, but if I try running another Recovery Point right after the successful Consistency Check, it fails again with the same error. This is affecting our nightly offsite backups to Azure, because all of the Recovery Points fail and then it has to run an automatic Consistency Check which causes the Azure backup job to fail with Error ID 33344, the latest disk backup already exits. Which means every day I have had to go into the Sever to send the last backup to Azure.


I have tried the following troubleshooting steps:

  1. Reinstalled the DPM Agent on the Hyper-V Hosts.
  2. Removed a protected Hyper-V Client and deleted the Replica Data on disk. Then reprotected the Data.
  3. Created a new Protection Group with one Hyper-V Host.


None have solved the problem. Interestingly, I have the same DPM Server protecting File Servers and SQL Servers and those have been running without issue.


Would love any suggestions to solve this.

Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
897 questions
0 comments No comments
{count} votes

Accepted answer
  1. Amardeep Saini 835 Reputation points Microsoft Employee

    Hello @Jeff Poblocki , Thank you for contacting us on Microsoft Q&A platform. Happy to help!

    This is to inform you that there is a regression on DPM 2022 UR2 which is causing the Hyper-V VM recovery point jobs to fail and leading for consistency check requirement every time.

    DPM Product Group is currently working to fix this issue and come up with a fix.

    Currently, till the issue is not fixed I would request you to modify the Protection Group and select the option 'Run a daily consistency check accordingly to the following schedule' and select the desire time you want to run the backup (also select the full backup time before CC schedule time). This will help you to complete the backup without manually run it till the time the issue is fixed.

    If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.

    2 people found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. XinGuo-MSFT 15,941 Reputation points


    Based on the symptoms you described, it seems that the replica is inconsistent and causing the backup to fail with Error ID 30135. One possible solution is to run a manual consistency check on the replica, which you mentioned you have already done.

    Another solution is to ensure that you're using the latest version of Microsoft Azure Backup Server and Data Protection Manager, and that the Automatic Consistency setting is enabled.

    You can also try restarting the services from the command prompt using the net stop dpmra command followed by net start dpmra.

    If none of these solutions work, you may need to contact the CSS support team for further assistance.

    User's image


    0 comments No comments