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
5 Resolve the list of possible failures.
6 Restart this server and reconnect or enable the network card again.
7 After restart, check that the Taskbar icon now reects the changes by showing P / – (Primary and passive).
8 On the Secondary active server or from a remote client, launch vCenter Server Heartbeat Console and
conrm that the Secondary server is reporting as active. If the Secondary server is not displaying as active,
perform the following steps:
a If the vCenter Server Heartbeat Console is unable to connect remotely, try running it locally. If you
are still unable to connect locally, use the Service Control Manager to verify that the service is running.
If the service is not running, review the event logs for a cause.
b Run the Congure Server wizard and conrm that the server identity is set to Secondary and the Active
Server is set to Secondary.
Note If vCenter Server Heartbeat is running, you can run the Congure Server wizard but any changes
made will not be saved.
c Verify that the protected application is accessible from clients. If accessible, start vCenter Server
Heartbeat on the Secondary server. If the application is not accessible, review the application logs to
determine why the application is not running.
d Start vCenter Server Heartbeat on the Secondary active server.
Note At this point, the data on the Secondary (active) server should be the most up to date and this
server should also be the live server on your network. When vCenter Server Heartbeat starts, it
overwrites all the protected data (congured in the File Filter list) on the Primary passive server. If
you are not sure that the data on the active server is the most current and up to date, contact VMware
Support (www.vmware.com/support). Go on to the next step only if you are sure that you want to
overwrite the protected data on the passive server.
e Start vCenter Server Heartbeat on the Secondary active server and check that the Taskbar icon now
reects the correct status by showing S / A (Secondary and active).
Applying Patches with vCenter Server Heartbeat Installed
If the Secondary server is the active server, skip step 1.
Procedure
1 Using the vCenter Server Heartbeat Console, select the Secondary server and clickMake Active. Wait for
Secondary server to become active.
2 Shutdown the vCenter Server Heartbeat Group, leaving the protected applications running on the Secondary
(active) server.
3 Using the Service Control Manager, congure VMware vCenter Server Heartbeat service Startup Type to
Manual on both Primary and Secondary servers.
VMware, Inc. 37
Chapter 3 Server Protection