Installation guide

Installation Guide
22 VMware, Inc.
 Software as specified in “Common Requirements” on page 20.
Secondary Server
The Secondary server operates as a near clone of the Primary server and must meet the following
requirements.
Hardware
Hardware should be equivalent to the Primary server to ensure adequate performance when the server is in
the active role:
 Similar CPU.
 Similar memory.
 Identical number of NICs to the Primary server.
 Drive letters must match the Primary server.
 Available disk space must be greater than or equal to the Primary server.
 Advanced Configuration and Power Interface (ACPI) compliance must match the Primary server. The
vCenter Server Heartbeat Standard implementation process assumes identical ACPI compliance on both
machines. If not, contact VMware Support at www.vmware.com/support for further information.
Software
Software on the Secondary server must meet the following requirements.
 OS version and Service Pack version must match the Primary server.
 OS must be installed to the same driver letter and directory as on the Primary server.
 Machine name must be different from the Primary server prior to installing vCenter Server Heartbeat.
 Set up in a workgroup prior to installing vCenter Server Heartbeat.
 System date, time, and time zone settings must be consistent with the Primary server.
Cloning Technology Options
Cloning the Primary server to create a nearly identical Secondary server involves different technologies
depending on the selected server architecture.
Cloning Prior to Installation
The following cloning technologies are supported for creating cloned images for use as a Secondary server
before you begin installing vCenter Server Heartbeat:
 VMware vCenter Converter for “Physical to Virtual” on page 21.
 VMware vCenter virtual machine cloning for “Virtual to Virtual” on page 21.
Cloning During Installation
Installation of vCenter Server Heartbeat provides support for NTBackup on Windows 2003 and Wbadmin on
Windows Server 2008 for automated cloning during the installation process. The process is automated but
requires meeting all prerequisites for the Secondary server specified in “Physical to Physical” on page 21.
Application Component Options
vCenter Server Heartbeat can accommodate any of the supported vCenter Server configurations and protects
the following components:
 vCenter Server Version 4.0