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
MaxDiskUsage Errors
vCenter Server Heartbeat uses queues to buer the ow of replication data from the active server to the passive
server. This conguration provides resilience in the event of user activity spikes, VMware Channel bandwidth
restrictions, or VMware Channel drops across a WAN deployment. Some types of le write activity also require
buering as they can cause a sharp increase in the amount of channel trac. The queues are called the send
queue (on the active server) or the receive queue (on the passive server).
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 lls. 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 congured for the maximum permitted queue size (by default, 1GB
on each server). You can congure both the queue location and the quota.
Two methods to set the queue size:
■
Using vCenter Server Heartbeat Console
1 Start vCenter Server Heartbeat
2 Open the vCenter Server Heartbeat Console, and select Data: Trac Queues.
3 Click Congure.
4 Congure the Allow a maximum value and click OK.
5 Shut down and restart vCenter Server Heartbeat to eect the change. You are not required to stop protected
applications.
■
Using the Server Conguration wizard
1 Shut down vCenter Server Heartbeat.
2 Open the Server Conguration wizard and select the Logs tab.
94 VMware, Inc.
Administrator Guide