L’équipe CSS a publié un billet sur le blog de l’équipe DPM concernant un problème survenant après l’application de l’Update Rollup 3 sur System Center 2012 R2 Data Protection Manager (DPM). Ce dernier survient quand vous sauvegardez des serveurs Hyper-V et que vous utilisez la fonctionnalité DPM Live Migration Tracking.
Depuis L’UR3, le service DpmVmmHelperService est désactivé engendrant des échecs de sauvegarde :
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)
Pour résoudre le problème, passez le service du démarrage Disabled à Manual.
Plus d’informations sur : http://blogs.technet.com/b/dpm/archive/2014/09/24/considerations-when-applying-update-rollup-3-for-system-center-2012-r2-data-protection-manager.aspx
