~ Dwayne Jackson
Hello, Dwayne Jackson II here. I wanted to take a minute today to detail a quick point to consider after applying Data Protection Manager (DPM 2012 R2) Update Rollup 3 (UR3) when Hyper-V protection is in place and you are using the DPM live migration tracking feature described here.
The issue is that after applying DPM 2012 R2 Update Rollup 3, DpmVmmHelperService is set to DISABLED instead of preserving the existing value which can cause Hyper-V backups to stop. When this occurs, the following error is displayed via DPM for backup failures:
Affected area: \Offline\<Virtual Machine Name>
Occurred since: Date Time
Description: Recovery point creation jobs for Microsoft Hyper-V \Offline\ <Virtual Machine Name> on <Virtual Machine Name>Resources. <Host Name>.contoso.com have been failing. The number of failed recovery point creation jobs = 1.
If the data source protected has some dependent data sources (like a SharePoint Farm), then click on the Error Details to view the list of dependent data sources for which recovery point creation failed. (ID 3114)
DPM was unable to establish a connection with the Virtual Machine Manager (VMM) server.
Server name: <Node Name>.contoso.com
Exception Message: Type: System.TimeoutException, Message: This request operation sent to net.tcp://<DPM Server Name>.contoso.com. The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. (ID 33400)
The issue is currently being investigated and future updates can be found here on our blog or in Data Protection Manager forum.
To navigate to announcements from the forum landing page, select Announcement and then scroll down to Hyper-V and CSV announcements.
1. After applying DPM 2012 R2 Update Rollup 3, open services on the DPM server. The DPM-VMM Helper Service startup type will be configured as Disabled.
2. Select the DPM-VMM Helper Service properties and adjust startup type to Manual as shown below.
Once this is done you should no longer see the issue.
Dwayne Jackson | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division
System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/