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. 81
Chapter 10 Troubleshooting
Send Queue
vCenter Server Heartbeat considers the active server’s send queue as unsafe because the data in this queue has
not yet been replicated across the VMware Channel to the passive server and therefore could be lost in the
event of a failover. As a result of failover, some data loss is inevitable, with the exact amount depending on the
relationship between available VMware Channel bandwidth and the required data transmission rate. If the
required data transmission rate exceeds available VMware Channel bandwidth, the send queue fills. If the
available VMware Channel bandwidth exceeds the required data transmission rate, the send queue empties.
This situation is most commonly seen in a WAN environment, where VMware Channel bandwidth is
restricted. In a LAN that normally has high bandwidth on a dedicated channel, the size of the send queue is
zero or near zero most of the time. On a server not protected with vCenter Server Heartbeat, all data is
technically unsafe and subject to loss if the server fails.
Receive Queue
The passive server’s receive queue is considered safe because the data in this queue already was transmitted
across the VMware Channel from the active server, and is not lost in the event of a failover, which applies all
updates to the passive server as part of the process.
Both send and receive queues are stored on disk by default in the <VMware vCenter Server Heartbeat
Install Directory>\R2\log directory, with a quota configured for the maximum permitted queue size
(by default, 1GB on each server). You can configure both the queue location and the quota.
Two methods to set the queue size:
Using vCenter Server Heartbeat Console
a Start vCenter Server Heartbeat
bOpen the vCenter Server Heartbeat Console, and select Data: Traffic Queues.
cClick Configure.
dSet the Allow a maximum value and click OK.
e Shut down and restart vCenter Server Heartbeat for the change to take effect. You are not required to
stop protected applications.
Using the Server Configuration wizard
a Shut down vCenter Server Heartbeat.
bOpen the Server Configuration wizard and click the Logs tab.
cSet the Maximum Disk Usage value and click Finish.
d Start vCenter Server Heartbeat.
MaxDiskUsage Error Messages
The following error messages display when available disk space on the servers is exceeded.
[L9]Exceeded the Maximum Disk Usage
(VCChannelExceededMaxDiskUsageException)
This message indicates that you have exceeded the amount of allocated disk space reserved for the queue.
Symptom
vCenter Server Heartbeat exceeds its preconfigured queue size.
N
OTE vCenter Server Heartbeat is a symmetrical system and can operate with either server in the active role.
For this reason, the queue size is always set to the same value for both servers.