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
Reference Guide
38 VMware, Inc.
Each target is allowed 5 seconds (default) to respond. On slower networks where latency and network
collisions are high, increase this interval by changing the Ping echo timeout value.
The failure of all three targets to respond is allowed up to the Auto-switchover if client network is lost for
threshold value. If the failure count of all three targets exceeds this value, vCenter Server Heartbeat initiates
an auto-switchover.
To enable Automatic Switchover in a WAN
1 In the vCenter Server Heartbeat Console, click the Network tab to display the Network Monitoring page.
2Click Configure Auto-switchover.
3 Select the Auto-switchover if client network connectivity lost for check box.
4 Configure the number of pings to wait before performing the auto-switchover.
5Click OK.
Setting Max Server Time Difference
vCenter Server Heartbeat generates a warning if the Primary and Secondary server system clocks are not
synchronized.
To override the warning
1Open the Server: Summary Configure dialog by clicking the Configure button.
2 Type a number (seconds) or use the arrow buttons to select an alert threshold value for time difference
between servers, which is checked at handshake following startup.
3Click OK.