One of the new features in service pack 1 for Data Protection Manager 2012 is the ability to scale out the protection of Hyper-V Clusters
Before SP1 there was a one to one relationship between a Hyper-V cluster and a DPM server , this had a impact of scale so the limiting factor in a Hyper-V cluster was the back engine.
There are a few limitations for this feature
It needs to be a fresh DPM install no upgraded
There is no support for DPM chaining
On the first install DPM server we push the agents to the Hyper-V hosts
And then on each of the Hyper-V Nodes
setdpmserver –add –dpmservername dpm02
On the next DPM server go to Agents – Install
Attach Agent Computer on trusted domain
Select the hyper-v nodes
And Attach them to the second DPM server
And we can now on both DPM servers attach VM’s for protection , note that there is no logic preventing your from double protecting a VM so make sure that the VM is only protected from one DPM server
Error 3184: DPM could not run the backup/recovery job for the data source because it is owned by a different DPM server.
Data source: \Backup Using Child Partition Snapshot\AZ01
Owner DPM Server: DPM02.internal.systemcenterdemo.dk.
So adding the same VM to mutiple DPM servers wont work , so adding VM’s to the DPM server should be automated to prevent fault
And after adding a DPM server more we now
have the same Hyper-V cluster protected with 3 DPM server , scale limit is 800ish VM pr DPM server but we are likely to hit the storage limit before that so scale-out is your friend.