You are here: Double-Take Availability requirements > Virtual workload requirements > Hyper-V to Hyper-V requirements

Hyper-V to Hyper-V requirements

Use these requirements if your source is a virtual server on a Hyper-V server, you want to protect the host-level virtual disk files, and your target is a virtual server on a Hyper-V server.

Source and target operating system—Your source and target servers can be any Windows 2008 or 2008 R2 operating system from the supported server operating systems 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.)
Source and target configurations—You can use one-to-one, many-to-one, or one-to-many configurations, however, you cannot use a chained configuration in a Hyper-V to Hyper-V to Hyper-V scenario.
Hyper-V configuration—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.

Clusters-Clustered Hyper-V hosts are not supported.
Ports—In addition to the standard Double-Take Availability ports that must be opened, you must also open port 135 for communication between the client and the servers.