6.4
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Configuring vCenter Server Heartbeat
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Application Protection Overview
- Applications: Applications Tab
- Reset the Application Health Status
- View Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Start and Stop Applications
- Configuring Applications
- Application Maintenance Mode
- Reviewing the State of an Application
- Reviewing the Applications Log
- Filtering Application Log Entries
- Applications: Services Tab
- Applications: Tasks Tab
- Applications: Plug-ins Tab
- Status and Control
- vCenter Server Heartbeat Console
- About vCenter Server Heartbeat Console
- Work with Groups and Pairs
- Add, Edit, Move, and Remove Pairs in VCenter Server Heartbeat Groups
- Review the Status of vCenter Server Heartbeat Groups and Pairs
- Exit vCenter Server Heartbeat Console
- Shut Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Client Plug-in
- Uninstall vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Troubleshooting Unexpected Behaviors
- Two Active Servers
- Two Passive Servers
- Synchronization Failures
- Registry Status is Out of Sync
- Channel Drops
- Subnet or Routing Issues
- MaxDiskUsage Errors
- MaxDiskUsage Error Messages
- [L9]Exceeded the Maximum Disk Usage (VCChannelExceededMaxDiskUsageException)
- [L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
- [L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
- [L20]Out of Disk Space (VCChannelOutOfDiskSpaceException)
- Application Slowdown
- Poor Application Performance
- Both Servers Can Accommodate the Initial Load but the Load Has Increased
- One Server Can Provide Adequate Resource Support, but the Other Cannot
- Scheduled Resource Intensive Tasks
- Glossary
VMware, Inc. 29
Chapter 3 Server Protection
When the vCenter Server Heartbeat pair establishes a connection, it triggers a file synchronization and
verification process to ensure all protected files on both server are identical. The process checks each 64K block
of each protected file and performs a checksum to determine whether the blocks differ. If the blocks are the
same, the block is marked as synchronized. If the blocks differ, then the block is replicated to the passive server
and then marked as synchronized. The file verification and synchronization process is finished after all blocks
of all stipulated files are marked as synchronized.
Monitoring the Status of Servers
The Server: Monitoring page provides additional information about the status of communications between
the servers within the pair. The graphical representation provides an overview of the status of
communications between the servers. A green channel icon indicates that the channel is connected and healthy
while a yellow dashed channel icon indicates that communications are not operational between the indicated
servers. In addition to the heartbeat sent between the servers, vCenter Server Heartbeat also sends a ping to
ensure that the servers remain visible to one another.
Configuring Heartbeat Settings
The Server: Monitoring page provides three configuration features: Configure Pings, Configure Failover,
and Configure Response Times.
Configure Pings
IP addresses of all NICs used for the VMware Channel are automatically added during installation. vCenter
Server Heartbeat, by default, added those IP addresses to the Server: Monitoring Ping Configuration dialog.
You can add additional targets to the list for each server’s channel connection in the event of redundant NICs.
The settings in the Server: Monitoring Ping Configuration dialog allow vCenter Server Heartbeat to send
pings across the VMware Channel in addition to the heartbeat (“I’m alive” messages) to confirm that the server
is still operational and providing service.
To configure pings
1Click Configure Pings to open the Server Monitoring: Ping Configuration dialog.
2Click on the Ping Settings tab to configure the Ping Interval.
3Click on the Ping Routing tab to add additional IP address for redundant NICs.
Configure Failover
The Failover timeout dictates how long vCenter Server Heartbeat waits for a missed heartbeat before it takes
a pre-configured action. This value is set to 60 seconds by default.
Table 3-3. Registry Synchronization Status
Status Icon Description
Checking The registry is currently in the process of synchronization.
Synchronized Fully synchronized
Error Not synchronized
Uninitialized