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
[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.
Problem
Replication stops and the vCenter Server Heartbeat Event Log displays the error message originating from the
passive server.
Cause
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 trac passes across the VMware Channel faster than it can be written to disk on the passive
server. The excess is buered 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 le 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.
Solution
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 le, and any
protected les help to alleviate disk performance issues:
1 Shut down vCenter Server Heartbeat.
2 Open the Server Conguration wizard and select the Logs tab.
96 VMware, Inc.
Administrator Guide