6.3
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Configuring vCenter Server Heartbeat
- Server Configuration Wizard
- Configuring the Machine Identity
- Configuring the Server Role
- Configuring the Client Connection Port
- Configuring Channel Routing
- Configuring the Default Channel Port
- Configuring Low Bandwidth Module
- Configuring Public IP Addressing
- Configuring for Identical Nodes
- Configuring for Non-Identical Nodes
- Managing vCenter Server Heartbeat License Keys
- Configuring Message Queue Logs
- Configuring the Maximum Disk Usage
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- 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
- Performance Protection
- Data Protection
- Data Protection Overview
- Other Administrative Tasks
- 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. 69
Chapter 10 Troubleshooting
Causes
ThemostcommonVMwareChannelconfigurationerrorsareasfollows:
VMwarevCenterServerHeartbeatPacketFilterisenabledononeormoreVMwareChannelNICs
VMwareChannelIPaddressesareconfiguredindifferentsubnets
InaWANimplementation,nostaticroutesexistbetweentheVMwareChannelNICs
Resolution
TheVMwareChannelconfigurationshouldbereviewedtoverifyproperconfiguration.
To resolve a VMware Channel configuration error
1DisabletheVMwarevCenterServerHeartbeatPacketFilteronVMwareChannelNICs.
2ConfiguretheVMwareChannelIPaddressesproperly.
3InaWANimplementation,configurestaticroutesbetweenVMwareChannelNICsproperly.
4DisableNetBIOSontheVMwareChannelNICs.
Incorrect or Mismatched Disk Configuration
WhenvCenterServerHeartbeatstarts,itchecksthecompletesetoffilefiltersforconsistency.
Symptom
Ifanyoftheentriespointstoanon‐existentdriveletterortoanon‐NTFSpartition,thelistoffilefiltersresets
tothedefaultvalueofC:\Protected\**.ThisisasafetymeasureasvCenterServerHeartbeatrequiresthe
samedriveletterconfigurationonthePrimaryandthe
Secondaryservers,andonlysupportsprotectionof
NTFSpartitions.
Cause
DifferentpartitionstructuresonPrimaryandSecondaryservers,suchthatoneormorefilefilterspointto
drivesthatcannotbeprotectedonbothservers.Forexample:
ThePrimaryserverhasdriveG,avalidNTFSpartition,butnocorrespondingdriveexistsonthe
Secondaryserver.
ThePrimaryserverhasdriveG,avalidNTFSpartition.TheequivalentdriveontheSecondaryserveris
aCDorDVDdrive,oraFATorFAT32partitionthatcannotbeprotected.
Ineitherscenario,ifyouconfigureafilefiltertoprotectadirectoryondriveG,theentire
filtersetisrejected
andthefiltersareresettothedefaultvalueof<Windows drive>\Protected\**.
Resolution
Followthestepsdocumentedinknowledgebasearticle1008458(vCSHB‐Ref‐500)TroubleshootingasetofFile
FiltersthatisresettoC:\Protected\**.
Passive Server Has Less Available Space than Active Server
Inadequateavailablediskspaceonthepassiveservercancausereplicationtocease.
Symptom
Replicationstopswiththefollowingerror:
[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.