You are here: Full server to Hyper-V protection > Full server to Hyper-V requirements

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.
Target server—The target server can be any Windows 2008 or 2008 R2 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 or Server Core 2008 R2 with the Hyper-V role enabled. (Hyper-V Server 2008 and Server Core 2008 are not supported.)
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.
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. You can install this version from the Double-Take CD, via a web connection during the Double-Take installation, or from a copy you have obtained manually from the Microsoft web site.

If you are installing on Server Core 2008 R2, .NET 3.5.1 functionality is included with the operating system but is disabled by default. You will need to enable it prior to installing Double-Take. See your Server Core documentation for the specific commands to enable the .NET functionality.

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

Configuration		Supported	Not Supported
Source to target configuration¹	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 configuration²	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 configuration³	Upgrade 5.2 physical or virtual server to Hyper-V connection to 6.0 full server to Hyper-V job	X
Upgrade configuration³	Upgrade 5.3 P/V to Hyper-V job to 6.0 full server to Hyper-V job	X

See Supported configurations for details on each of the source to target configurations.
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.
When upgrading from version 5.2, you can keep your existing job, but you will need to upgrade to version 5.3 first, then upgrade to version 6.0. If you want to upgrade directly to version 6.0, you will have to delete your job and re-create it. 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.