Installation guide
Table Of Contents
- Installation Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Installation
- vCenter Server Heartbeat Implementation
- Installing vCenter Server Heartbeat
- Unattended Installation of vCenter Server Heartbeat
- Appendix - Setup Error Messages
- Glossary
VMware, Inc. 21
Chapter 2 vCenter Server Heartbeat Implementation
When installing into a Windows Server 2008 or 2008 R2 environment, verify that Windows Server Backup
Feature and Command Line Tools have been installed on the Primary and Secondary servers prior to
installing vCenter Server Heartbeat. Installation of Windows Server Backup Feature and Command Line
Tools will also install Windows PowerShell.
Server Architecture Options
The selected server architecture affects the requirements for hardware and the technique used to clone the
Primary server.
Virtual to Virtual
Virtual to Virtual is the supported architecture if vCenter Server is already installed on the production
(Primary) server running on a virtual machine. Benefits to this architecture include reduced hardware cost,
shorter installation time, and use of the Pre-Clone technique for installation.
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
Each virtual machine used in the Virtual to Virtual pair must be on a separate ESX host to guard against
failure at the host level.
Each virtual NIC must use a separate virtual switch.
Physical to Virtual
The Physical to Virtual architecture is used when the environment requires a mix of physical and virtual
machines, such as when vCenter Server is installed on a physical server in an environment where available
hardware is limited. This architecture is appropriate if you must avoid adding more physical servers or if you
plan to migrate to virtual technologies over a period of time. With Physical to Virtual architecture, you can test
vCenter Server running in a virtual environment or migrate from Physical to Virtual without any downtime.
The Secondary virtual machine must meet the minimum requirements.
The specifications of the Secondary virtual machine must match the Primary physical server as follows:
Similar CPU
Identical Memory
The Secondary virtual machine must have sufficient priority in resource management settings so that
other virtual machines do not impact its performance.
Each virtual NIC must use a separate virtual switch.
Physical to Physical
The Physical to Physical architecture is used in environments where both the Primary and Secondary servers
are physical servers. Use of Physical to Physical limits installation options as it requires cloning using vCenter
Server Heartbeats native cloning during the installation process. This architecture requires attention to detail
when preparing for installation as both hardware and software must meet specific prerequisites.
Primary Server
The Primary server must meet the following requirements:
Hardware as specified in “Common Requirements” on page 20.