Specifications
Table Of Contents
- Reference Guide
- Contents
- About This Book
- Getting Started
- Installation
- vCenter Server Heartbeat Implementation
- vCenter Server Heartbeat Installation on Windows Server 2003
- vCenter Server Heartbeat Installation on Windows Server 2008
- Configuring vCenter Server Heartbeat
- Server Configuration Wizard
- Configuring the Machine Identity
- Configuring the Server Role
- Configuring the Client Connection Port
- Configuring Channel IP Routing
- Configuring the Default Channel Port
- Configuring Low Bandwidth Module
- Configuring Public IP Addressing
- Enabling Network Monitoring
- Configuring Split-Brain Avoidance
- Managing vCenter Server Heartbeat License Keys
- Configuring Message Queue Logs
- Configuring the Maximum Disk Usage
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Status and Control
- Performance Protection
- Data Protection
- Data Protection Overview
- Other Administrative Tasks
- 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
- Appendix - Setup Error Messages
- Glossary
VMware, Inc. 125
Chapter 6 Server Protection
When the vCenter Server Heartbeat pair establishes a connection, it triggers a file synchronization and
verification process to ensure all the files stipulated through file filters are mirror images of one another on
their respective servers. The process checks each 64K block of all protected files and performs a checksum to
find differences between blocks. When the checksum is the same, the block is marked as synchronized. When
the blocks are different, the block is replicated to the passive server and then marked as synchronized. The file
verification and synchronization process completes when all blocks of all files are marked as synchronized.
Configuring Heartbeat Settings
The Heartbeat interval dictates the time step at which the passive server sends Heartbeat packets to the active
server across the VMware Channel connections. Max Heartbeats Missed Before Failover determines the
number of missed packets before initiating a failover.
1Click Advanced > Communication on the left navigation pane and click the Configuration tab.
2Set Max Heartbeats Missed Before Failover and the Heartbeat Interval and click Apply.
Table 6-2. File and Registry Status
Icon Description
The files or registry are fully synchronized.
Files are present that are currently not checked. A full system check has not completed.
The registry is currently in the process of being synchronized.
The differences in the registry are currently being checked to see if they are synchronized.
The files or registry are not synchronized.