I have a three-node server 2012R2 Hyper-V failover cluster backing up to a Server 2012R2 running DPM 2012R2 RU5. All three cluster nodes are connected to an iSCSI SAN using CSV volumes. Windows backup is installed on the cluster nodes and the DPM server. The Hyper-V role is also installed on the DPM server. The VMs have the current integration services installed and enabled.
All of the Hyper-V hosts installed the DPM agent correctly and are backing up to the DPM server. When I add one of the virtual machines to a protection group, the first attempted replica fails with this error:
"DPM failed to communicate with dpmserver.domain because of a communication error with the protection agent. (ID 53 Details: Not implemented (0x80000001))"
It fails after just under two minutes with 0 data transferred. I noticed that this alert says it is failing to communicate with the DPM server and not the client agent.
From there the DPM server continues to attempt consistency checks that fail with this error:
"An unexpected error occurred while the job was running. (ID 104 Details: The RPC server is unavailable (0x800706BA))"
It also fails after just under two minutes with 0 data transferred.
I have disabled all firewalls and that hasn't helped. If I watch the Hyper-V host, I can see a checkpoint get created for the VM and then the VM says "backing up". After the ~2 minutes it merges and deletes the checkpoint. I also watch process and TCP connections and don't see any failed attempts.
I'm adding the VM to the protection group on the DPM server by choosing to modify the protection group. Then I expand the Hyper-V cluster, Hyper-V, and select the \online\VMName item. It modifies the protection group and says it's creating the initial replica which fails with the errors above.
So, it looks like DPM is reaching in and checkpointing the VM, but it is not streaming it back to the DPM server.
Any insight into what I'm missing would be really appreciated.