6.4
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Configuring vCenter Server Heartbeat
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Application Protection Overview
- Applications: Applications Tab
- Reset the Application Health Status
- View Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Start and Stop 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
- Status and Control
- vCenter Server Heartbeat Console
- About vCenter Server Heartbeat Console
- Work with Groups and Pairs
- Add, Edit, Move, and Remove Pairs in VCenter Server Heartbeat Groups
- Review the Status of vCenter Server Heartbeat Groups and Pairs
- Exit vCenter Server Heartbeat Console
- Shut Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Client Plug-in
- Uninstall vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Troubleshooting Unexpected Behaviors
- Two Active Servers
- Two Passive Servers
- Synchronization Failures
- Registry Status is Out of Sync
- Channel Drops
- Subnet or Routing Issues
- MaxDiskUsage Errors
- MaxDiskUsage Error Messages
- [L9]Exceeded the Maximum Disk Usage (VCChannelExceededMaxDiskUsageException)
- [L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
- [L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
- [L20]Out of Disk Space (VCChannelOutOfDiskSpaceException)
- Application Slowdown
- Poor Application Performance
- Both Servers Can Accommodate the Initial Load but the Load Has Increased
- One Server Can Provide Adequate Resource Support, but the Other Cannot
- Scheduled Resource Intensive Tasks
- Glossary
VMware, Inc. 75
Chapter 10 Troubleshooting
Causes
The most common VMware Channel configuration errors are as follows:
VMware vCenter Server Heartbeat Packet Filter is enabled on one or more VMware Channel NICs
VMware Channel IP addresses are configured in different subnets
In a WAN implementation, no static routes exist between the VMware Channel NICs
Resolution
The VMware Channel configuration should be reviewed to verify proper configuration.
To resolve a VMware Channel configuration error
1 Disable the VMware vCenter Server Heartbeat Packet Filter on VMware Channel NICs.
2 Configure the VMware Channel IP addresses properly.
3 In a WAN implementation, configure 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 file filters for consistency.
Symptom
If any of the entries points to a non-existent drive letter or to a non-NTFS partition, the list of file filters resets
to the default value of C:\Protected\**. This is a safety measure as vCenter Server Heartbeat requires the
same drive letter configuration on the Primary and the Secondary servers, and only supports protection of
NTFS partitions.
Cause
Different partition structures on Primary and Secondary servers, such that one or more file filters 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 configure a file filter to protect a directory on drive G, the entire filter set is rejected
and the filters are reset to the default value of <Windows drive>\Protected\**.
Resolution
Follow the steps documented in knowledge base article 1008458 (vCSHB-Ref-500) Troubleshooting a set of File
Filters that is reset to C:\Protected\**.
Passive Server Has Less Available Space than Active Server
Inadequate available disk space on the passive server can cause replication to cease.
Symptom
Replication stops with the following error:
[N27]Failed to write information for the file: {filename} to the disk. Either the disk is full or
the quota (for the SYSTEM account) was exceeded.