You are here: Agentless Hyper-V protection > Agentless Hyper-V requirements

Agentless Hyper-V requirements

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

Source and target host operating system—Your source and target host servers 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.) In each case, the source and target must be running identical operating system versions. For example, your source cannot be Windows 2008 and your target Windows 2008 R2.
Guest operating systems—The guest operating system can be any operating system. However, if you want Double-Take to monitor the virtual machine for failover, then you must have Integration Components installed on the guest operating system and the virtual machine must be powered on.
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.
Virtual machine configurations—The following limitations apply to the virtual machines on the source and target Hyper-V servers.

The virtual machines must be in their own home folder that is not shared by any other virtual machines.
The virtual machines cannot be created in or replicated to the Hyper-V system default folder.
The virtual machines' snapshot folder must be unique to each virtual machine, they cannot be in the Hyper-V system default folder, and they cannot be changed once protection has been established.
The virtual machines cannot use raw, pass-through, or differencing disks.
If a source virtual machine is configured for dynamic memory, the replica virtual machine will automatically be configured for dynamic memory. You cannot configure the replica differently.

IP addressing—IPv4 is the only supported IP version.
WAN support—If your source and target are across a WAN and you want Double-Take to automatically update networking on the guest operating system during failover, the following limitations apply. If you choose not to have Double-Take automatically update networking on the guest operating system during failover, you will have to update the network manually, but the following limitations will not apply.
- Guest operating system—The guest operating system must be Windows 2003, 2008, or 2012.
- Windows Management Instrumentation (WMI)—The host and guest operating systems must have the WMI service enabled.
- User Access Control (UAC)—UAC must be disabled on the guest operating system.
- Name resolution—You must establish name resolution for the guest operating system.
Microsoft .NET Framework—Microsoft .NET Framework version 3.5 Service Pack 1 is required on the source and target. 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. If you are using Windows 2008 or 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.If you are using Windows 2008 R2 or later, you can enable it through Windows features.
Live migration—Windows 2012 live migration is supported for CSV clustered virtual machines, but the shared-nothing configuration is not supported. If a virtual machine is migrated, Double-Take will automatically start a remirror.

Supported configurations—The following table identifies the supported configurations for an agentless Hyper-V job. (These are source and target configurations for the host, not the virtual machines.)

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 ^3,4	X
Upgrade configuration⁵	Upgrade 5.3 Hyper-V to Hyper-V job to 7.0 agentless Hyper-V job	X
Upgrade configuration⁵	Upgrade 6.0 host-level Hyper-V job to 7.0 agentless Hyper-V job	X
Version 7.0 console^6,7	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

See Supported configurations for details on each of the source to target configurations.
Windows 2008 R2 and 2012 are the only supported versions of clustered Hyper-V servers. Windows 2008 R1 is not supported for clustering.
CSV support at the host-level is for Windows 2012 only. Although CSV is not supported for host-level protection for Windows 2008, you can use host-level protection for non-CSV virtual machines on a CSV configured cluster. To do this, you will need to execute the altitude script located in the \tools\scripts\csv directory on the product DVD or in the extracted web download files. If you copy the altitude.bat file to another location, be sure and copy the two .reg files as well. To protect non-CSV virtual machines on a CSV configured cluster, run the following command on each node of the cluster.

altitude default

The default script will cause your cluster to go into redirected (maintenance) mode the next time the CSV is brought online, taken offline, or changes owning nodes.

If you change back to CSV virtual machines on your CSV configured cluster, you will need to run the following command to change Double-Take back to the correct configuration for CSV functionality.

altitude target

The target script will keep your cluster from going into redirected (maintenance) mode.
If the host containing your source virtual machines is a CSV configuration, the virtual disks must be on the same CSV volume. Different CSV volumes for the source virtual disks is not supported.
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. If you are using a cluster configuration, you cannot upgrade. You must delete the existing job, upgrade all of your nodes, and then re-create the job.
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.
Newer job options available in the version 7.0 console will not be functional when creating jobs for servers running version 6.0.