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

ESX to ESX requirements

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

ESX servers—The ESX servers that will host your source and target can be any of the following operating systems. Note that ESX versions listed are commonly referred to as the Classic edition.

ESX 3.5.x Standard, Advanced, or Enterprise
ESX 4.0.x Standard, Advanced, Enterprise, or Enterprise Plus

Note:

If your source and target are running on different versions of ESX, ideally, the target should be a newer version of ESX. If your source must be a newer version of ESX than the target, you must take into consideration ESX features that are supported on the newer version on the source (like VmxNet enhanced or additional virtual NICs available) that will not be supported on the earlier target version of ESX.

VirtualCenter—Although VirtualCenter is not required, it is recommended. If you are using it, then you must use version 2.5 or later.

Note:

VMotion is only supported if you are using VirtualCenter.

Do not use MSDE for the VirtualCenter database.

Double-Take Availability for VMware Infrastructure service and console—The service and console can be run from a physical or virtual machine running Windows 7, Windows Vista, or Windows XP, or any of the supported server operating systems.
Ports—In addition to the standard Double-Take Availability ports that must be opened, you must also open ports 22, 443, and 6331 on the source and target servers.
E-mail notification—In order to use automatic e-mail notification, you must add VI_Service.exe to the exception list of most anti-virus and spam filters. In addition, you may need to open port 25 in your anti-trust software to allow SMTP e-mail.