5.5

QuickStart Guide
12 VMware, Inc.
 VirtualCenter Server 2.5 Update 2
 VirtualCenter Server 2.5 Update 3
 VirtualCenter Server 2.5 Update 4
 VirtualCenter Server 2.5 Update 5
 vCenter Server 4.0
 vCenter Server 4.0 Update 1
 Operating System
 Windows Server 2003 SP1 or SP2 x86
 Windows Server 2003 SP2 x64
 Windows Server 2008 SP1 or SP2 x86
 Windows Server 2008 SP1 or SP2 x64
 Prior to installing vCenter Server Heartbeat, verify that vCenter Guided Consolidation, vCenter Update
Manager, and vCenter Converter are configured using Fully Qualified Domain Names (FQDN) rather
than IP addresses.
 During the setup process, vCenter Server Heartbeat verifies that a minimum of 1GB RAM is available. To
ensure proper operation, vCenter Server Heartbeat requires a minimum of 1GB RAM (2GB is
recommended) in addition to any other memory requirement for the Operating System or vCenter Server.
 Verify that 2GB of disk space is available on the installation drive for vCenter Server Heartbeat.
 Obtain and use local administrator rights to perform vCenter Server Heartbeat installation.
 Apply the latest Microsoft security updates.
 All applications that will be protected by vCenter Server Heartbeat must be installed and configured on
the Primary server prior to installing vCenter Server Heartbeat.
 Verify that both Primary and Secondary servers have identical system date, time, and time zone settings.
Once configured, do not change the time zone.
 Verify that the Principal (Public) network adapter is listed as the first network adapter in the network
connections bind order. (Network Connections > Advanced > Advanced Settings).
 Verify that the Managed IP setting in the Virtual Infrastructure Client is the same IP address used for the
vCenter Server Heartbeat Principal (Public) IP address.
Server Architecture Options
The selected server architecture affects the requirements for hardware and the technique used to clone the
Primary server.
Virtual to Virtual (V2V)
V2V is the supported architecture if vCenter Server is already installed on the production (Primary) server
running on a virtual machine. The Secondary virtual machine must meet the minimum requirements.
 The specifications of the Secondary virtual machine must match the specifications of the Primary virtual
machine as follows:
 Similar CPU (including resource management settings)
 Memory configuration (including resource management settings)
 Appropriate resource pool priorities
 OS version and Service Pack