You are here: Double-Take Availability requirements > Cluster workload protection requirements

Cluster workload protection requirements

Standard cluster—If you will be protecting a standard cluster configuration, with a shared SCSI disk, there are two additional requirements.
Network—The cluster's private network should be a unique subnet so that Double-Take Availability will not attempt to use an unreachable private network.
Volumes—The source and target should have identical drive mappings.
GeoCluster—If you will be protecting a GeoCluster configuration, where data is stored on volumes local to each node, there are several additional requirements.
Operating system—The operating systems are limited to the Windows Enterprise, Itanium, and Datacenter editions listed in the source and target server requirements.
Volumes—The source and target should have identical drive mappings.
Hardware—Intel-based hardware is required. Microsoft support for MSCS and MSCS-based Microsoft applications requires that the cluster configuration appear on the Microsoft Hardware Compatibility List under category Cluster.
Cluster Network Name—Double-Take Availability does not handle dynamic changes to the cluster network names, the names assigned to the routes for network traffic. If a network name is changed for a network that is used by a GeoCluster Replicated Disk resource, the resource must be taken offline, the resource's network property must be changed, and then the resource must be brought back online.
Protocols and Networking—All of the networking requirements below must be met.
TCP/IP connection between nodes on the same logical IP subnet
Your network can contain direct LAN connections or VLAN technology.
The maximum round trip latency between nodes should be no more than ½ second.
Multiple networks are recommended to isolate public and private traffic.