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. 83
Chapter 10 Troubleshooting
Resolution
To resolve this issue:
If you have multiple physical disks on each server, locate the vCenter Server Heartbeat send and receive
queues on a separate physical disk, away from the Windows directory, the Windows page file, and any
protected files help to alleviate disk performance issues:
a Shut down vCenter Server Heartbeat.
bOpen the Server Configuration wizard and click the Logs tab.
c Set the path for Message Queue Logs Location and click Finish.
d Start vCenter Server Heartbeat on both servers.
The selected path is applied to all vCenter Server Heartbeat queues on both servers.
Increase the amount of disk space allotted to the queues. However, if a hardware issue is the root of the
problem, correct that problem at the source.
The size of the passive server’s receive queue can increase sharply in response to certain types of file write
activity on the active server, such as when vCenter Server Heartbeat is replicating a large number of very
small updates of a few bytes each. The volume of update traffic can be far greater than the physical size
of the files on the disk, and the receive queue can become disproportionately large. You can see this
pattern of disk activity during the population of Full-Text Catalogs in Microsoft SQL Server. Increase the
amount of disk space available for the queues. Move the queues to their own physical disk, upgrade the
memory or the disk subsystem.
vCenter Server Heartbeat requires a certain amount of system resource for its own basic operations and
requires some additional resources for processing replication traffic. This is in addition to the resources
used by Windows and other applications running on the server, including critical applications protected
by Heartbeat. Allocate sufficient resources for all the applications and services running on such a server
to provide maximum performance, stability, and resilience for changing client, server, and network
activity.
[L20]Out of Disk Space (VCChannelOutOfDiskSpaceException)
This message indicates that one of the servers in the pair has run out of disk space without reaching its preset
quota.
Symptom
Replication stops and the vCenter Server Heartbeat Event Log displays the error message originating from
either server in the pair.
Cause
One of the queues has exceeded the amount of physical disk space available for it without reaching its quota
limit. For example, if the maximum queue size is set to 5GB, but only 3GB of physical disk space remains, this
error message is reported if one of the queues exceeds 3GB in size.
Resolution
Free up more disk space or move the queues to a disk with sufficient free space to accommodate queue sizes
up to the limit configured for Maximum Disk Usage.