DPM 2016 won't refresh Hyper-V members to add to protection groups RRS feed

  • Question

  • Looks to be a similar issue folks were having in 2012 R2.  DPM 2016 UR2 (5.0.322) installed, backing up only hyperv data sources.  It's wired up to all of our vhosts (a mix of 2012 r2 and 2016), but after I move a VM to a new vhost, it doesn't appear on the list even after clicking Refresh.  I'm seeing the issue on both 2012 R2 and 2016 vhosts.

    I've refreshed the connection from the agent list and rebooted the DPM server, but to no avail.  On the 2016 box, I made sure all of the vms have had their configurations updated to 8.0 so it can take advantage of RCT, but it doesn't seem to have any bearing on whether it shows up on the list.

    I don't like the idea of not being protected if and when I have to move a vm to a different host -- and if this is something being fixed in UR4, can we get a hotfix so I don't have to wait until fall?

    Sunday, June 25, 2017 12:41 PM