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
Adding a Service
To protect a service that was not automatically added by vCenter Server Heartbeat during installation, the
service must be added through the vCenter Server Heartbeat Console and be in a Running state.
Procedure
1 Right-click on a service and select Add from the menu or click Add on Applications: Services page to invoke
the Add Service dialog. The Name drop-down list contains a list of all currently running services.
2 Select the service and set the values for Target State on Active and Target State on Passive. Normally the
Target State on Active is set to Running and the Target State on Passive is set to Stopped.
Note Setting the target state for both the active and passive server to Running can cause the service to
place a lock on some les preventing synchronization from completing.
3 If vCenter Server Heartbeat is to manage the start and stop of the service, select Manage Starting and
Stopping. If vCenter Server Heartbeat is to monitor the state of the service, select Monitor State.
vCenter Server Heartbeat also assigns three sequential tasks to perform in the event of failure. Task options
include Recover Service, Application Restart, Log Warning, Switchover, and any additional user-dened tasks
previously created.
4 Assign a task to each of the three failure options and click OK.
If an application with the failure option set to Application Restart fails, only the services that have failed
are restarted. Dependent services do not stop and restart as a result of the failure.
Editing a Protected Service
Once a protected service has been added and congured, you can change the action to take upon failure and
other options using the Edit Service dialog.
Procedure
1 Select the service and click Edit.
The Edit Service dialog opens to provide a subset of same options available when adding a new service.
2 Make the modications and click OK.
Editing All Protected Services
vCenter Server Heartbeat Console allows you to perform a single operation to congure the actions to take
upon failure for all protected services.
Procedure
1 Click Edit All.
The Edit Services dialog opens to provide the actions to take upon failure for all three instances. Selections
made in the Edit Services dialog will be applied to all protected services.
2 Select the action to take for First, Second, and Third failure and then click OK.
VMware, Inc. 49
Chapter 5 Application Protection