Hello,
We are using 2012 R2 DC to create a Hyper-V 2 node cluster. The backup is DPM 2012 R2 running on 2012 R2 DC. The DPM system was upgraded to 2012 R2 from DPM 2010 about a year ago and has worked for the most part.
Two problems we are having. I am using the VSS writer from the SAN manufacture. On our old cluster I used the Microsoft VSS writer and had no problems unless I loaded the C: up with too many files on the cluster node. I saw another post
that says to disable the HW VSS writer but that was unsuccessful the last time I tried it. I am going to try it again though.
1. I currently get a random VM that hangs during the backup. The VM still runs but I cannot migrate it and backups fail from that point on. In Hyper-V backup the Status field shows "Backing up...". I am waiting for this to happen on a non critical VM but alas that is not happening. <sigh> To correct the problem I have to pull power from the cluster node the system was on and then about 90% of the time I have to replace to different .sys files in c:\windows\system23\drivers and then run the startup repair utility from the windows install disk.
2. I did not notice this until this week but my BMR backups of the Hyper-V hosts are taking over 12 hours to complete. The BMR on a different stand alone server is taking less than 10 min. What is causing this and if these are taking this long is it interfering with the backup of the VMs on the cluster and causing the problem in paragraph 1 above? I have tried to stagger my backups so they don't interfere with each other but if this one is taking 12-14 hours that will never happen.