5.5
Table Of Contents
- QuickStart Guide
- Contents
- About This Book
- vCenter Server Heartbeat Introduction
- vCenter Server Heartbeat Installation
- Installation Verification
QuickStart Guide
14 VMware, Inc.
Set up 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 near identical Secondary server involves different techniques
depending on the selected server architecture.
Supported Pre-Clone Technologies
The following cloning technologies are supported for creating Pre-Cloned images for use as a Secondary
server:
VMware Converter for “Physical to Virtual (P2V)” on page 13.
VMware vCenter virtual machine cloning for “Virtual to Virtual (V2V)” on page 12.
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 13.
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 vCenter Server
VMware Capacity Planner
VMware Converter Enterprise
VMware Update Manager
VMware License Server
vCenter Server Version 4.0
VMware vCenter Server
VMware Guided Consolidation Service
VMware License Sever
VMware ADAM
VMware vCenter Management Web Server
VMware Update Manager
VMware Converter Enterprise
VMware Orchestrator
VMware vSphere Host Update Utility
vCenter Server with SQL Server on the Same Host
To ensure adequate performance in 20+ host or 200+ virtual machine environments, VMware recommends that
SQL Server and vCenter Server be installed on separate physical disk drives. VMDKs must be on separate
datastores to avoid potential disk bottlenecks.
N
OTE Ensure that all VMware components are bound to the Principal (Public) IP address on the Principal
(Public) network adapter and that the Principal (Public) network adapter is listed first in the bind order of the
Network Connections > Advanced > Advanced Settings window.