You are here: Double-Take Availability overview > Configurations > Supported Hyper-V source protection workload configurations

Supported Hyper-V configurations

To protect Hyper-V virtual machines, your environment must conform to the following requirements.

The source virtual machine be in its own home folder that is not shared by any other virtual machines.
The source virtual machine cannot be created in the Hyper-V system default folder.
The source virtual machine cannot be replicated into the Hyper-V system default folder on the target host.
The replica virtual machine folder on the target must be unique to the replica virtual machine.
The source virtual machine snapshot folder must be unique to the virtual machine, and it cannot be in the Hyper-V system default folder.
The replica virtual machine snapshot folder cannot be the Hyper-V system default folder.
The replica virtual machine cannot share a snapshot folder with any other virtual machines.
After protection has been configured for a virtual machine, the location of the snapshot folder for that virtual machine cannot be changed. If the snapshot folder is changed, the protection job must be removed and re-created.
If a protected virtual machine is renamed in the Hyper-V manager, the replica virtual machine will not be renamed. In order to pick up the name change, the protection job must be removed and re-created.
Virtual machines cannot use raw, pass-through, or differencing disks.
Clustered Hyper-V source and target environments are not supported.

The following host configurations are supported for protecting Hyper-V virtual machines:

Many to One—Virtual machines from multiple Hyper-V hosts can be protected on a single Hyper-V target host.
One to One—Virtual machines from a single Hyper-V host can be protected on a single Hyper-V target host.
Many to Many—The Double-Take Console can manage multiple Hyper-V source and target hosts, allowing you to protect virtual machines from multiple Hyper-V hosts on multiple Hyper-V targets.

The following host configuration is not supported:

Chained configurations—You cannot protect virtual machines to a target Hyper-V host, and then in turn protect those virtual machines from the first target host to an additional target Hyper-V host.