6.6
Table Of Contents
- vCenter Server Heartbeat Administrator's Guide
- Contents
- About This Book
- Introduction
- vCenter Server Heartbeat Monitoring
- Supported vCenter Server Heartbeat Clients
- vCenter Server Heartbeat Console
- vSphere Web Client Plug-in
- vSphere Client Plug-in
- Server Monitoring
- Network Monitoring
- Application Monitoring
- Performance Monitoring
- Monitoring Data Replication
- Managing vCenter Server Heartbeat
- Server Configuration Wizard
- Managing Heartbeat Settings
- Managing Application Protection
- Managing Services
- Managing Tasks
- Managing Rules
- Managing Plug-ins
- Managing Data Protection
- Maintaining vCenter Server Heartbeat
- vCenter Server Heartbeat Diagnostics
- Collecting Diagnostic Logs
- Two Active or Two Passive Nodes
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Node 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
In additional to those listed above, vCenter Server Heartbeat Server: Summary page provides the following
additional controls:
■
Start Applications – Click to start protected applications on the active node.
■
Stop Applications – Click to stop protected applications on the active node.
■
Configure – Click to open the Configure dialog. Select the radio button corresponding to whether you
want to stop or leave the protected applications running when vCenter Server Heartbeat is shut down.
You can select whether to leave protected applications running upon shutdown when a net stop command
is issued, and to start protected applications upon startup when a net start command is issued. Type a
number (seconds) or use the arrow buttons to select an alert threshold value for time difference between
nodes, which is checked at handshake following startup. Click OK.
Controlled Shutdown
A Controlled Shutdown is a process where vCenter Server Heartbeat service is able to delay system shutdown
long enough to perform all necessary steps required to stop applications and replication in a synchronized
state. Controlled Shutdown is intended for situations where an unattended planned shutdown of the node is
necessary. When configured via the vCenter Server Heartbeat Console Data: Replication page, this feature
allows vCenter Server Heartbeat to gracefully shutdown in the absence of the administrator.
Configuring Controlled Shutdown
Procedure
1 Navigate to vCenter Server Heartbeat Console's Data: Replication page.
2 Click Configure.
3 On the Replication Configuration dialog, select the Controlled Shutdown tab.
4 Select the nodes on which to enable Controlled Shutdown.
5 Select the days and hours parameters under which the node(s) will perform Controlled Shutdown.
6 Configure the length of time for node(s) to wait for Controlled Shutdown.
Note The ability to configure the length of time for the node(s) to wait for the Controlled Shutdown is
configurable on Windows Server 2008 but is not configurable on Windows Server 2003.
When the Fast Check process is enabled in addition to Controlled Shutdown, vCenter Server Heartbeat
can be scheduled to perform unattended restarts of the system while maintaining synchronization of data.
For more information about Fast Check, see Configuring Fast Check .
Application Maintenance Mode
Use the Applications: Summary page to disable application protection and service monitoring for maintenance
purposes.
To perform manual maintenance:
72 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide