6.4
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Configuring vCenter Server Heartbeat
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Application Protection Overview
- Applications: Applications Tab
- Reset the Application Health Status
- View Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Start and Stop 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
- 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
- Controlled Shutdown
- vSphere Client Plug-in
- Uninstall vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- 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
VMware, Inc. 51
Chapter 6 Status and Control
The status hyperlinks in this overview window links to pages that provide more specific related information
and management controls.
Click:
The Server connection name to view the Server: Summary page
The Applications status to view the Applications: Summary page
The Network status to view the Network Monitoring page
The File System or Registry status to view the Data: Replication page
Exit vCenter Server Heartbeat Console
1Click Exit on the File menu. The Confirm Exit message appears.
2Click Yes.
Shut Down Windows Without Stopping vCenter Server Heartbeat
Always stop vCenter Server Heartbeat before attempting to shut down Microsoft Windows. If an attempt is
made to shut down Windows without stopping vCenter Server Heartbeat, a confirmation message is
displayed. When the confirmation message is displayed, click Cancel and stop vCenter Server Heartbeat
before attempting Windows shut down again.
Controlled Shutdown
A Controlled Shutdown is the process where the VMware vCenter Server Heartbeat service is able to delay a
system shutdown for a sufficient period to perform all of the necessary steps required to stop the applications
and replication in a synchronized state. The Controlled Shutdown is intended for situations where an
unattended planned shutdown of the server is necessary. When configured in the vCenter Server Heartbeat
Console Data: Replication page, this feature allows vCenter Server Heartbeat to gracefully shutdown in the
absence of the administrator.
To configure Controlled Shutdown:
1 Navigate to the Data > Replication page of the vCenter Server Heartbeat Console.
2Click the Configure button.
3 Select the Controlled Shutdown tab of the Replication Configuration dialog.
4 Select the servers on which to enable Controlled Shutdown.
5 Select the days and hours parameters under which the server(s) will perform Controlled Shutdown.
6 Configure the length of time for the server(s) to wait for the Controlled Shutdown.
N
OTE The ability to configure the length of time for the server(s) to wait for the Controlled Shutdown is
configurable on Windows Server 2008 but is not configurable on Windows Server 2003.