Export (0) Print
Expand All

Prerequisites for virtual machine protection

Updated: November 1, 2013

Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager

This topic summarizes the prerequisites in System Center 2012 - Data Protection Manager (DPM) for the protection of virtual machines that are located on servers that are running Hyper-V.

Server prerequisites

  1. Install the Hyper-V role on the DPM server. DPM protects Hyper-V virtual machines even without the role, but you cannot perform item-level recovery (ILR) unless the role is installed.

  2. Ensure that the server that acts as the server that is running Hyper-V meets Hyper-V requirements. For more information, see Install the Hyper-V Role and Configure a Virtual Machine.

  3. Install the following updates on the server that is running Hyper-V:

  4. For a Cluster Shared Volumes (CSV) deployment, install the Volume Shadow Copy Services (VSS) hardware provider on the server that is running Hyper-V. Contact your storage area network (SAN) vendor for the VSS hardware provider.

  5. Ensure that the following updates are installed on the target server that is 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.
        This update provides increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role.

      • KB956697. This update can be applied when the Hyper-V VSS writer appears to be missing due to the presence of corrupt virtual machine configuration files on the server that is running Hyper-V.

      • KB958184. This update can be applied when virtual machine files are saved on a volume that is mounted on a failover cluster by using a volume GUID.

      • KB959962 on the servers that are running Hyper-V. This update for Hyper-V VSS writer is required if the backup fails for one of the following reasons:

        • A transient VSS error occurs, but the operation can be retried.

        • The provider for the VSS application writer is not working as expected

        • The recovery of a virtual machine fails because it has legacy network adapters that are attached.

        Following this update, the Hyper-V Integration Services on each of the virtual machines that are running on the server must be updated by inserting the Integration Services Disk from the Action menu in the viVMM console. For this update, the virtual machine must be restarted.

      • KB960038. This update can be applied on all servers that are running Hyper-V. This update for Windows Server 2008 fixes a crashing problem of the server that is running Hyper-V, which you might experience when the Hyper-V VSS writer is used for backups.

    • The version of Integration Components that is running on the virtual machine should be the same as the version of Hyper-V on the server that is running Hyper-V. For Hyper-V RTM, the version is 6.0.6001.18016.
      You can confirm this version number in the Device Manager on the guest virtual machine. In Device Manager, under System Devices, right-click Hyper-V Volume Shadow Copy, and then click Properties. Check the version on the Driver tab. If the version does not match, insert the Integration Services disk by selecting the option under the Action menu in the VMM console. Install the integration components, and then restart the virtual machine.

Supported scenarios

DPM can protect the following Hyper-V topologies:

  • Protects virtual machines that are hosted on stand-alone servers that are running Hyper-V and that use local or directly attached storage.

  • Protects virtual machines that are running on a cluster that uses Cluster Shared Volumes (CSV) storage.

  • Protects virtual machines that are running on a stand-alone server or cluster that use Server Message Block (SMB) 3.0 file server storage.

  • Protects virtual machines that are running during a live migration.

Unsupported scenarios

  • DPM servers and servers that are running Hyper-V must be located in the same domains. Different domains are not supported.

  • DPM does not support the backup of virtual machine data on pass-through disks that present volumes to the virtual machine or use a remote virtual hard disk (VHD). For such virtual machines, we recommend that you perform a backup of the VHD files at the level of servers that are running Hyper-V by using DPM and install a DPM protection agent on the virtual machine to back up data that is not visible on the server that is running Hyper-V.

  • DPM does not support backup and recovery of virtual machines on replica servers that are running Hyper-V.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft