6.3

VMware, Inc. 9
1
This chapter includes the following topics:
 “vCenter Server Heartbeat Concepts” on page 9
 “vCenter Server Heartbeat Switchover and Failover Processes” on page 15
Overview
vCenter Server Heartbeat is a Windows based service specifically designed to provide high availability
protection for vCenter Server configurations without requiring any specialized hardware.
vCenter Server Heartbeat Concepts
Architecture
vCenter Server Heartbeat software is installed on a Primary (production) server and a Secondary
(ready-standby) server. These names refer to the physical hardware (identity) of the servers.
Depending on the network environment, vCenter Server Heartbeat can be deployed in a Local Area Network
(LAN) or Wide Area Network (WAN). Additionally, vCenter Server Heartbeat allows for installation using
identical nodes (LAN and WAN) or non-identical nodes (LAN only). These features provide flexibility
necessary to address most network environments.
Depending on the network environment and architecture selected, vCenter Server Heartbeat can be
configured where the Primary and Secondary server have the same domain name and Principal (Public) IP
address (identical nodes) or where the Primary and Secondary servers have different domain names but share
the Principal (Public) IP address (non-identical nodes). In either architecture, the Secondary server will have
the same file and data structure and can run all of the same applications and services as the Primary server.
The vCenter Server Heartbeat software is symmetrical in almost all respects, and either the Primary server or
the Secondary server can take the active role and provide protected applications to the user.
When deployed, vCenter Server Heartbeat uses two servers with either identical Principal (Public) IP
addresses for identical nodes or a shared Principal (Public) IP address for non-identical nodes. One of the
servers performs the role of the active server that is visible on the Public network while the other is the passive
server that is hidden from the Public network but remains as a ready-standby server. Only one server can
display the Principal (Public) IP address and be visible on the Public network at any given time.
Identical Nodes Configuration
When configured for identical nodes, vCenter Server Heartbeat uses two servers with the same domain name,
Principal (Public) network IP address, file and data structure, applications, and services to ensure that vCenter
Server is running and available. With a packet filter installed on both servers Principal (Public) NICs, vCenter
Server Heartbeat applies the packet filter to the Principal (Public) NIC on the passive server thereby blocking
communications and hiding the passive server from the Public network. When a switchover occurs, the packet
Introduction
1