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
Reference Guide
36 VMware, Inc.
7Afterrestart,checkthattheTaskbariconnowreflectsthechangesbyshowingP/–(Primaryandpassive).
8OntheSecondaryactiveserverorfromaremoteclient,launchvCenterServerHeartbeatConsoleand
confirmthattheSecondaryserverisreportingasactive.
IftheSecondaryserverisnotdisplayingas
active,performthefollowingsteps:
1IfthevCenterServerHeartbeatConsoleisunabletoconnectremotely,tryrunningitlocally.Ifyouarestill
unabletoconnectlocally,usetheServiceControlManagertoverifythattheserviceisrunning.Ifthe
serviceisnotrunning,reviewtheeventlogsfor
acause.
2RuntheConfigureServerwizardandconfirmthattheserverissettoSecondaryandactive.
3Verifythattheprotectedapplicationisaccessiblefromclients.Ifaccessible,startvCenterServerHeartbeat
ontheSecondaryserver.Iftheapplicationisnotaccessible,reviewtheapplicationlogstodeterminewhy
the
applicationisnotrunning.
4StartvCenterServerHeartbeatontheSecondaryactiveserver.
5StartvCenterServerHeartbeatontheSecondaryactiveserverandcheckthattheTaskbariconnow
reflectsthecorrectstatusbyshowingS/A(Secondaryandactive).
Configuring Split-Brain Avoidance
Split‐brainAvoidanceensuresthatonlyoneserverbecomesactiveiftheVMwareChannelconnectionislost,
butbothserversremainconnectedtothePrincipal(Public)network.Split‐brainAvoidanceworksbypinging
fromthepassiveservertotheactiveserveracrossthePrincipal(Public)network.Iftheactiveserverresponds,
thepassiveserverdoesnotfailover,eveniftheVMwareChannelconnectionislost.WANinstallationsrequire
differentIPaddressesonthePrincipal(Public)networkforthelocalandremoteservers.
ToenableSplit‐brainAvoidance,opentheServer:MonitoringpageinthevCenterServerHeartbeatConsole,
clickConfigureFailover,
andselectPreventfailoverifchannelheartbeatislostbutActiveserverisstill
visibletootherservers(recommended).
YoumustconfigureManagementIPaddressesonthePrincipal(Public)networkcardsofeachservertoallow
thepassiveservertosendaping.ManagementIPaddressesareadditionalIPaddressesassigned
tothe
networkcardconnectedtothePrincipal(Public)network.Theyareusedtoallowthepassiveserverto
communicate,becauseunlikethePrincipal(Public)IPaddress,theyarenotfiltered.Thisallowsthepassive
servertosendpings,andisalsorequiredtoallowthepassiveservertosend
emailalerts.Toconfigurea
ManagementIPaddressonthePrincipal(Public)networkcard,followtheprocedurebelow.
To configure a Management IP address:
1OpenthenetworkpropertiesforthePrincipal(Public)networkconnection.
2Double‐clickTCP/IPtodisplaytheproperties.
3ClickAdvanced.
4Enteranadditional(currentlyunused)IPaddressinthetable.
5 RepositiontheIPaddressesin
thelistsothattheadditional(Management)IPaddressappearsfirst,and
thePrincipal(Public)networkaddress(bywhichclientsconnecttotheserver)appearssecond.
N
OTEIfvCenterServerHeartbeatisrunning,youcanruntheConfigureServerwizardbutanychanges
madewillnotbesaved.
N
OTEAtthispoint,thedataontheSecondary(active)servershouldbethemostuptodateandthis
servershouldalsobetheliveserveronyournetwork.WhenvCenterServerHeartbeatstarts,itoverwrites
alltheprotecteddata(configuredintheFileFilterlist)onthePrimarypassive
server.Ifyouarenotsure
thatthedataontheactiveserveristhemostcurrentanduptodate,contactVMwareSupport
(www.vmware.com/support).Goontothenextsteponlyifyouaresurethatyouwanttooverwritethe
protecteddataonthepassiveserver.