DPM 2012 R2 UR13 – can not add clustered VMs to protection group (ID 36)


Just wanted to share with you recent issue with DPM 2012 R2 and Hyper-V failover cluster with few nodes Windows 2012 R2 and hundreds VMs. ┬áIt was a while since I installed UR 13 on DPM, but few days ago I found I can’t modify or create protection groups anymore, I only could see the clustered object, but I could not expland it to get it’s resources:

Sometimes I got DPM ID 36 error:

DPM cannot access the (vmname) because part of the path has been deleted or renamed

Check the path and enter it again

The cluster’s nodes and DPM servers were restarted but it didn’t help. Also I noticed all DPM servers connected to this cluster have similar issues. The case in Microsoft Premier Support was opened. After some troubleshooting, we found that DPM can backup only those VMs, which are running on Hyper-V host with newly installed DPM agent.

So solution is: reinstall DPM agents on all cluster’s nodes, just remove them from “Add/Remove Programs”. No reboot required, just delete this key in registry after installation – HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent\2.0\Restart Pending” . If you have more than one DPM server, you have to add permissions with command “BIN_DPM_DIR\.setdpmserver -add -DPMServername dpm_server_name” on each cluster’s node.

You may also like


  1. More info would be helpful. How exactly did Microsoft have you reinstall the protection agents on your cluster nodes? Where in the registry is the “Require Reboot” entry?

    1. Hi Pete!
      Thanks for your questions!
      The article has been update in order to provide more detailed information. Hope this helps or ask me if it’s unclear for you!

      Best regards,

  2. Hi, I tried the solution with no joy. I kept getting the error message. In my case, the solution was a lot simpler:

    1- Remove the role of the VM with the error from the Failover Cluster Manager
    2- Rename the VM name using Hyper-V Manager
    3- Add the VM back to the Failover Cluster Manager
    4- Use the DPM wizard to add the VM to the Protection Group. Use the button to “refresh” the data source from the cluster

    1. Thanks Jose Angel Rivera . Your solution did the trick for me, too. Still don’t know why it chocked on a simple name like “Dev1” but it did. Renaming VM worked.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.