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
VMware Channel Incorrectly Configured
If the VMware Channel is not properly congured, it cannot initiate the handshake to establish communications
through the VMware Channel connection.
Problem
Failure to establish the VMware Channel connection prevents a full system check, thereby leaving the File
System Status and Registry Status as Out-of-sync.
Cause
The most common VMware Channel conguration errors are as follows:
■
VMware vCenter Server Heartbeat Packet Filter is enabled on one or more VMware Channel NICs
■
VMware Channel IP addresses are congured in dierent subnets
■
In a WAN implementation, no static routes exist between the VMware Channel NICs
Solution
The VMware Channel conguration should be reviewed to verify proper conguration.
1 Disable the VMware vCenter Server Heartbeat Packet Filter on VMware Channel NICs.
2 Congure the VMware Channel IP addresses properly.
3 In a WAN implementation, congure static routes between VMware Channel NICs properly.
4 Disable NetBIOS on the VMware Channel NICs.
Incorrect or Mismatched Disk Configuration
When vCenter Server Heartbeat starts, it checks the complete set of le lters for consistency.
Problem
If any of the entries points to a non-existent drive letter or to a non-NTFS partition, the list of le lters resets
to the default value of C:\Protected\**. This is a safety measure as vCenter Server Heartbeat requires the same
drive letter conguration on the Primary and the Secondary servers, and only supports protection of NTFS
partitions.
Cause
Dierent partition structures on Primary and Secondary servers, such that one or more le lters point to
drives that cannot be protected on both servers. For example:
■
The Primary server has drive G:, a valid NTFS partition, but no corresponding drive exists on the Secondary
server.
■
The Primary server has drive G:, a valid NTFS partition. The equivalent drive on the Secondary server is
a CD or DVD drive, or a FAT or FAT32 partition that cannot be protected.
In either scenario, if you congure a le lter to protect a directory on drive G:, the entire lter set is rejected
and the lters are reset to the default value of <Windows drive>\Protected\**.
Solution
◆
Follow the steps documented in knowledge base article 1008458 (vCSHB-Ref-500) Troubleshooting a set of
File Filters that is reset to C:\Protected\**.
VMware, Inc. 87
Chapter 10 Troubleshooting