6.6
Table Of Contents
- vCenter Server Heartbeat Administrator's Guide
- Contents
- About This Book
- Introduction
- vCenter Server Heartbeat Monitoring
- Supported vCenter Server Heartbeat Clients
- vCenter Server Heartbeat Console
- vSphere Web Client Plug-in
- vSphere Client Plug-in
- Server Monitoring
- Network Monitoring
- Application Monitoring
- Performance Monitoring
- Monitoring Data Replication
- Managing vCenter Server Heartbeat
- Server Configuration Wizard
- Managing Heartbeat Settings
- Managing Application Protection
- Managing Services
- Managing Tasks
- Managing Rules
- Managing Plug-ins
- Managing Data Protection
- Maintaining vCenter Server Heartbeat
- vCenter Server Heartbeat Diagnostics
- Collecting Diagnostic Logs
- Two Active or Two Passive Nodes
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Node 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
Solution
To resolve this issue:
■
If you have multiple physical disks on each node, 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:
1 Shut down vCenter Server Heartbeat.
2 Open the Server Configuration wizard and select the Logs tab.
3 Configure the path for Message Queue Logs Location and click Finish.
4 Start vCenter Server Heartbeat on both nodes.
Note The selected path is applied to all vCenter Server Heartbeat queues on both nodes.
■
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 node’ s receive queue can increase sharply in response to certain types of file write
activity on the active node, 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 node, including critical applications protected by
Heartbeat. Allocate sufficient resources for all the applications and services running on such a node 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 nodes 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 node 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 sufficient free space to accommodate queue
sizes up to the limit configured for Maximum Disk Usage.
VMware, Inc. 93
Chapter 5 vCenter Server Heartbeat Diagnostics