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
Installation Guide
12 VMware, Inc.
filteronthecurrentlyactiveserverisenabledpreventingcommunicationsonthePublicnetworkwhilethe
packetfilteronthecurrentlypassiveserverisdisabledtherebyallowingthetwoserverstoswitchroles.From
thispointon,thepreviouslypassiveserverisnowactiveandservicingtheclients.Thepreviouslyactive
server
isnowpassiveandhiddenfromthePublicnetwork.
Intheeventofafailover,thepreviouslyactiveserverisdeemedtohavefailedandnofurtheractionsare
necessary.Thepacketfilteronthepreviouslypassiveserverisdisabledallowingtheservertobecomevisible
onthePublic
networkandserviceclientsasthenewactiveserver.
Advantages of Identical Nodes Configuration
IdenticalnodeconfigurationprovidesforasimplifiedinstallationandsupportsVirtualtoVirtual,Virtualto
Physical,andPhysicaltoPhysicalarchitectures.Additionally,identicalnodeconfigurationsupportsuseof
boththePre‐cloneandInstallclone,installationtechniques.Whenconfiguredwithidenticalnodes,
vCenter
ServerHeartbeatprovidestwoidenticalserversthatcanfunctionastheactiveserverservicingclients.
Additionally,withidenticalnodes,organizationscandeployvCenterServerHeartbeatinWANenvironments
therebyextendingprotectionoverwidegeographicdistances.
Non-Identical Nodes Configuration
Non‐identicalnodeconfigurationprovidesenhancedmanagementcapabilitiestothevCenterHeartbeat
Serverclusterbyprovidingcontinuousaccesstothepassiveserversimultaneouslywhiletheactiveserver
continuestoserviceclients.Whenconfiguredwithnon‐identicalnodes,vCenterServerHeartbeatusesunique
servernamesforeachserverandenhancedIPaddress
managementcapabilitiestoaccommodateMicrosoft
(updatable)DNSserversandLockedDownmodeornon‐MicrosoftDNSserverswhileprovidingthesame
levelsofprotectionaswhenconfiguredwithidenticalnodes.
TheSecondaryserverhasadifferentFullyQualifiedDomainName(FQDN)thanthePrimaryserverbutuses
thesamefile
anddatastructure,samePrincipal(Public)networkaddress,andcanrunallthesame
applicationsandservicesasthePrimaryserver.WithvCenterServerHeartbeatsoftwaresymmetricalin
almostallrespects,eitherthePrimaryserverortheSecondaryservercanassumetheactiveroleandprovide
protectedapplicationstotheuser.
Additionally,thisconfigurationallowsthepassiveservertobeeasilyaccessedformaintenancepurposes,
updatinganti‐virusdefinitionfiles,receivingoperatingsystemhot‐fixes,updatesandpatchesfrom
third‐partymanagementsoftware,andallowsuseofthird‐partymonitoringtools.
Switchover/Failover Without Updating DNS Servers
SelecttheNon‐IdenticaloptionwhenyouwanttodeployvCenter
ServerHeartbeatwithnon‐identicalnodes
inanenvironmentthatdoesnotpermitupdatingDNS(anon‐updatableMicrosoftDNSserver(orLocked
DownMode)oranon‐MicrosoftDNSserver).ThisconfigurationrequiresvCenterServervCenterServer4.0
Update1orlater,ifSQLServerisdeployed,itmust
beremote,andsinceDNSwillnotbeupdated
automatically,youmustprepopulatetheDNSserverwithentriesforthenewmanagementnamesandIP
addressesofthePrimaryandSecondaryservers.vCenterServerHeartbeatusespermanentlyassignedunique
ManagementIPaddressesonboththePrimaryandSecondaryservers.AdjacentIP
addressesshouldbe
reservedandusedforthePrincipal(Public)IPaddressandtheManagementIPaddressesforthePrimaryand
SecondaryServerswheninstallingvCenterServerHeartbeatonnon‐identicalnodesonserversrunning
Windows2008.WhenvCenterServerHeartbeatisstarted,thesharedPrincipal(Public)IPaddressis
provided
totheactiveserver.Whenaswitchoveroccurs,thesharedPrincipal(Public)IPaddressisremovedfromthe
previouslyactiveserver(makingitpassive)andprovidedtothepreviouslypassiveserver(makingitactive)
allowingtheserverstoswitchrolesandthenewactiveservertobeginservicingclients.
Microsoft DNS Server Updated During Switchover/Failover
Select
theNon‐identical(UpdatesMSDNS)optionwhenyouwanttodeployvCenterServerHeartbeatwith
non‐identicalnodesinanenvironmentwherevCenterServer4.0Update1orlaterisinstalled,ifSQLServer
isdeployeditmustberemote,aMicrosoftDNSserverthatpermitsupdatesisused,
andyouwanttotake
advantageoftheenhancedpassiveservermanagementcapabilities.vCenterServerHeartbeatinteractswith
theDNSserverandfollowingaswitchover,willensurethatserversarecorrectlyidentifiedonthenetworkby
updatingDNSinformation.vCenterServerHeartbeatusesuniqueservernamesandManagementIP