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
76 VMware, Inc.
Cause
The passive server has less available disk space than the active server, preventing updates from being
replicated to the passive server. The quantity of updates from the active server exceeds the passive server's
available disk space.
Resolution
Free up some additional disk space on the passive server. Do not delete data from the protected set to prevent
data loss in the event of a switchover. You could update the disk subsystem on the passive server. After
allocating space, start replication.
Registry Status is Out of Sync
The Registry can be reported as Out of sync when one or more Registry keys fail to synchronize.
Resource Issues
Inadequate resources can cause poor performance and prevent the registry from synchronizing.
Symptom
vCenter Server Heartbeat logs the following error message:
Call to RegOpenKeyEx failed: on <Reg_Key>: Insufficient system resources exist to complete the
requested service.
Cause
One or both of the servers are running low on virtual memory.
Resolution
Restart the server to free up virtual memory.
Registry Security Issues
Inability to access the registry prevents replication of the registry.
Symptom
vCenter Server Heartbeat is unable to read, sync, or replicate the registry.
Cause
If a protected registry key has permissions that deny Write access to the System account, this can prevent
vCenter Server Heartbeat from synchronizing or replicating it.
Resolution
Change the permissions on the affected registry key to grant the System account Full Control.
Channel Drops
When the VMware Channel loses connection between the servers, the following scenarios can occur.
Performance Issues
Poor performance can be experienced as a result of a channel loss.