6.3

VMware, Inc. 25
Chapter 2 vCenter Server Heartbeat Implementation
 VMware vCenter virtual machine cloning for “Virtual to Virtual (V2V)” on page 23.
Supported Install Clone Technologies
Installation of vCenter Server Heartbeat provides support for NTBackup on Windows 2003 and Wbadmin on
Windows Server 2008 for automated Install Cloning. This process is automated but requires meeting all
prerequisites for the Secondary server specified in “Physical to Physical (P2P)” on page 24.
Application Component Options
vCenter Server Heartbeat can accommodate any of the supported vCenter Server configurations and protects
the following components:
 VirtualCenter Server Version 2.5
 VMware VirtualCenter Server
 VMware Capacity Planner
 VMware Converter Enterprise
 VMware Update Manager
 VMware License Server
 VMware Virtual Infrastructure Client
 vCenter Server Version 4.0
 VMware vCenter Server
 VMware Guided Consolidation Service
 VMware License Server
 VMware ADAM
 VMware vCenter Management Web Server
 VMware vCenter Update Manager
 VMware vCenter Converter
 VMware vCenter Orchestrator
 VMware vSphere Host Update Utility
 VMware vSphere Client
 vCenter Server Version 4.1
 VMware vCenter Server
 VMware Guided Consolidation Service
 VMware License Sever
 VMware ADAM
 VMware vCenter Management Web Server
 VMware vCenter Update Manager
 VMware vCenter Converter
 VMware vCenter Orchestrator
 VMware vSphere Host Update Utility
 VMware vSphere Client
 View Composer 1.1 and 2.0
 VMware View Composer
 VMware Universal File Access
N
OTE When using the Install Clone technique in a Physical to Virtual (P2V) architecture, VMware Tools must
not be installed on the Secondary (cloned) server during the vCenter Server Heartbeat installation process. If
VMware Tools are currently installed on the Secondary (cloned) server, you must fully uninstall VMware
Tools prior to initiation of the Setup process. Once the installation of vCenter Server Heartbeat has completed,
you may reinstall VMware Tools.