Open topic with navigation

Full server to Hyper-V requirements

In addition to the Core Double-Take requirements, use these requirements for full server to Hyper-V protection.

• Source server—The source server can be any physical or virtual server running any of the operating systems listed in the Core Double-Take requirements. However, if you are using a Windows 2003 operating system, you must have Service Pack 2 which is required for Hyper-V Integration Services. Additionally, your source cannot be a Hyper-V server.

• Target server—The target server can be any Windows 2008, 2008 R2, or 2012 operating system from the Core Double-Take requirements that has the Hyper-V role enabled. In addition, you can use Hyper-V Server 2008 R2, Server Core 2008 R2, or Server Core 2012 with the Hyper-V role enabled. (Hyper-V Server 2008 and Server Core 2008 are not supported.)

• Server Core—In addition to the Server Core requirements above, there is a Server Core limitation. DNS updates are not supported for Server Core servers.

• Disk types—Virtual machines can use raw, pass-through, or differencing disks, however, they will be virtual hard disks on the replica on the target.

• IP addressing—IPv4 is the only supported IP version.

• Microsoft .NET Framework—Microsoft .NET Framework version 3.5 Service Pack 1 is required. This version is not included in the .NET version 4.0 release. Therefore, even if you have .NET version 4.0 installed, you will also need version 3.5.1. For Windows 2008 and earlier, you can install this version from the Double-Take DVD, via a web connection during the Double-Take installation, or from a copy you have obtained manually from the Microsoft web site. For Windows 2008 R2 and later, you need to enable it through Windows features.

• Snapshots—You can take and failover to Double-Take snapshots using a full server to Hyper-V job. See Core Double-Take requirements for the specific snapshot requirements.

• Supported configurations—The following table identifies the supported configurations for a full server to Hyper-V job.

  Configuration		Supported	Not Supported
  Source to target configuration1	One to one, active/standby	X
  	One to one, active/active		X
  	Many to one	X
  	One to many	X
  	Chained		X
  	Single server		X
  Server configuration2	Standalone to standalone	X
  	Standalone to cluster		X
  	Cluster to standalone	X
  	Cluster to cluster		X
  	Cluster Shared Volumes (CSV) guest level	X
  	Cluster Shared Volumes (CSV) host level		X
  Upgrade configuration3	Upgrade 5.3 P/V to Hyper-V job to 7.0 full server to Hyper-V job	X
  	Upgrade 6.0 full server to Hyper-V job to 7.0 full server to Hyper-V job	X
  Version 7.0 console4,5	Version 7.0 console can create job for 5.3 source and 5.3 target		X
  	Version 7.0 console can create job for 6.0 source and 6.0 target	X
  	Version 7.0 console can create job for 7.0 source and 7.0 target	X

  1. See Supported configurations for details on each of the source to target configurations.
  2. Supported cluster configurations can be used to protect a node, shared storage, or a virtual machine, however, there is no cluster resource or cluster-awareness with this configuration.
  3. When upgrading from version 5.3, you can perform a rolling upgrade where you update the target server first. After the upgrade is complete, the source will automatically reconnect to the target. At this point, the job will be an unmanaged job that you can delete or failover. No other job controls will be available. Once you upgrade you source, the job will be fully controllable.
  4. Once you upgrade your console to version 7.0, existing jobs that are running version 5.3 will not appear in the console until the target of the job is upgraded to version 7.0.
  5. Newer job options available in the version 7.0 console will not be functional when creating jobs for servers running version 6.0.

Related Topics