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
82 VMware, Inc.
Causes
On the active server, the size of the active server queue has exceeded the disk quota allocated for it. On the
passive server, the size of the passive server queue has exceeded the disk quota allocated for it.
Resolution
While neither condition is critical, determine the sequence of events that led to the condition.
[L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
This message indicates that you have exceeded the amount of allocated disk space reserved for the active
server’s send queue.
Symptom
Replication stops and the vCenter Server Heartbeat Event Log displays the error message originating from the
active server.
Causes
A temporary interruption in the VMware Channel, or insufficient VMware Channel bandwidth to support the
volume of replication traffic starts filling the active server queue. The size of the queue eventually exceeds the
configured disk quota.
Resolution
Assuming no other channel connection issues exist (see knowledge base article 1008551 (vCSHB-Ref-992) -
Troubleshooting VMware vCenter Server Channel Drops), you can increase the amount of disk space allotted to the
queues. The default setting is 1GB, which can be insufficient on servers with a large volume of replication
traffic and limited VMware Channel bandwidth. If you have sufficient disk space, set the queue size to zero
(unlimited) so vCenter Server Heartbeat can use any free disk space to store the queues.
[L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
This message indicates that you have exceeded the amount of allocated disk space reserved for the passive
server’s receive queue.
Symptom
Replication stops and the vCenter Server Heartbeat Event Log displays the error message originating from the
passive server.
Causes
Two of the most common causes are shown below:
The bottleneck lies between the VMware Channel NIC and the disk subsystem on the passive server.
Replication traffic passes across the VMware Channel faster than it can be written to disk on the passive
server. The excess is buffered temporarily in the passive server’s receive queue. The size of the queue can
eventually exceed the allotted disk quota.
If the passive server is much less powerful than the active server in terms of processor speed, RAM, or
disk performance, it can lag behind the active server during periods of high replication activity. Monitor
one or more Windows performance counters to determine the component experiencing sustained high
activity. Intensive page file use or persistently large disk queue length can indicate a problem. Upgrade
one or more physical components of the server.
Either server can be active or passive. If the Secondary server is more powerful than the Primary server,
hardware-related issues can only occur while the Secondary server is in the active role.