Prerequisites for Hyper-V protection

Before protecting Hyper-V virtual machines with System Center 2012 – Data Protection Manager (DPM), ensure that the following updates are installed on the target server running Hyper-V:

• The customer should be running Hyper-V RTM. The corresponding Windows update is KB950050.
  
  
• Install the following updates:
  
  
  • KB951308 on each cluster node for cluster deployment.
    Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role.
    
    
  • KB956697. This update may be applied when the Hyper-V writer seems to go missing due to the presence of corrupt Virtual Machine configuration files in the server running Hyper-V.
    
    
  • KB958184. This update may be applied when virtual machine files are saved on a volume mounted on a failover cluster using a volume GUID.
    
    
  • KB959962 on the Hyper-V hosts. This update for Hyper-V writer is required if the backup fails for one of the following reasons:
    
    
    • Retryable VSS error.
      
      
    • VSS application writer provider is going to bad state.
      
      
    • If recovery of a virtual machine is failing because it has legacy network adapters attached.
      
      
    Following this update, the integration services on each of the virtual machines running on the server must be updated by inserting the Integration Services Disk from the Action menu in the virtual machine’s management console. This will require the virtual machine to restart.
    
    
  • KB960038 on all Hyper-V hosts. This update for Windows Server 2008 fixes a crash of the Hyper-V host server which you may experience when backups are made using Hyper-V writer.
    
    
• The version of Integration Components running inside the VM should be the same as the version of Hyper-V on the host. For Hyper-V RTM it is 6.0.6001.18016.
  You can confirm this in the Device Manager inside the guest VM. Under System Devices in Device Manager, right-click the entry Hyper-V Volume Shadow Copy and choose Properties. Check the version under the Driver tab. If the version does not match, insert the integration services disk by choosing the option under the Action menu in the VM console. Install the integration components and reboot the VM.