6.5
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Introduction
- Configuring vCenter Server Heartbeat
- Server Protection
- Checking the Server Pair Status
- Monitoring the Status of Servers
- Configuring Heartbeat Settings
- Network Protection
- Application Protection
- Applications: Summary Tab
- Resetting the Application Health Status
- Viewing Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Stop and Start 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
- Applications: Summary Tab
- Status and Control
- About vCenter Server Heartbeat Console
- Working with Groups
- Working with Pairs in vCenter Server Heartbeat Groups
- Reviewing the Status of vCenter Server Heartbeat Groups and Pairs
- Exiting vCenter Server Heartbeat Console
- Shutting Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Web Client Plug-in
- Uninstalling vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Two Active or Two Passive Servers
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Server Does Not Meet Minimum Hardware Requirements
- Hardware or Driver Issues on VMware Channel NICs
- Firewall Connection
- Channel Fails to Connect After Configuring Firewall Ports
- Incorrect VMware Channel Configuration
- VMware vCenter Server Heartbeat Packet Filter Is Enabled on the Channel NIC(s)
- Subnet or Routing Issues
- MaxDiskUsage Errors
- Application Slowdown
- Glossary
3 Congure the path for Message Queue Logs Location and click Finish.
4 Start vCenter Server Heartbeat on both servers.
Note 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 le 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 trac can be far greater than the physical size
of the les 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 trac. This is in addition to the resources
used by Windows and other applications running on the server, including critical applications protected
by Heartbeat. Allocate sucient 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.
Problem
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.
Solution
◆
Free up more disk space or move the queues to a disk with sucient free space to accommodate queue
sizes up to the limit congured for Maximum Disk Usage.
Application Slowdown
Operations performed by the application can take longer to complete, and in turn, can aect the time required
to log in to a remote client, or to open or save a le. This is true for both servers running vCenter Server
Heartbeat and for servers running any other application. vCenter Server Heartbeat can monitor system
performance counters and display warnings when predened thresholds are exceeded, but it does not actively
manage system resources for other applications. Like any other application, it also requires a nite amount of
resources for its own operations in addition to the resources used by the operating system and the protected
application.
VMware, Inc. 97
Chapter 10 Troubleshooting