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
If vCenter Server should fail, vCenter Server Heartbeat rst tries to restart the application on the active server
(1) in Figure 1-2.
If the application does not successfully restart, vCenter Server Heartbeat initiates a switchover (2) in Figure
1-2. Refer to “vCenter Server Heartbeat Switchover and Failover Processes,” on page 15 for further information
about the switchover process.
Figure 1- 2. Switchover
A switchover gracefully closes vCenter Server running on the active server and restarts it on the passive server,
including the component or service that caused the failure. For example, if the Primary server is active and
the Secondary server is passive, the Primary server is demoted to a passive role and is hidden from the network
when the Secondary server is promoted to an active role and is made visible to the network. The mechanics
of switchovers are discussed in more detail later in this guide.
Performance Protection
Ensuring that vCenter Server is operational and providing service at an adequate level of performance to meet
user demands is important. The vCenter Server Heartbeat plug-in provides these monitoring and pre-emptive
repair capabilities.
vCenter Server Heartbeat proactively monitors system performance attributes and can notify the system
administrator in the event of a problem. Additionally, it can be congured to take pre-emptive action to prevent
an outage.
In addition to monitoring vCenter Server services, vCenter Server Heartbeat can monitor specic attributes to
ensure that they remain within normal operating ranges. Similar to application monitoring, various rules can
be congured to trigger specic corrective actions whenever these attributes fall outside of their respective
ranges.
vCenter Server Heartbeat provides the same level of exibility to dene and perform multiple corrective actions
in the event of problems on a service by service or even attribute by attribute basis.
Data Protection
You can congure vCenter Server Heartbeat to protect the application environment. All data les that users
or the vCenter Server requires in the application environment are made available should a failure occur. After
installation, vCenter Server Heartbeat congures itself to protect les, folders, and registry settings for vCenter
Server on the active server by mirroring them in real time to the passive server. If a failover occurs, all les
protected on the failed server are available to users after the failover, hosted on the Secondary server.
12 VMware, Inc.
Administrator Guide