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
Reference Guide
34 VMware, Inc.
iv On the Primary server, launch the vCenter Server Heartbeat Configure Server wizard and click
the Machine tab. In the Active server section select Primary.
v Restart vCenter Server Heartbeat on the Primary Server and allow the system to synchronize.
vi Start the vCenter Server Heartbeat Console and verify that the system completes the Full System
Check.
8 Change the Role of the server to Secondary/passive:
a Launch the vCenter Server Heartbeat Configure Server Wizard and click the Machine tab. In the
Active server section select Primary.
b Reboot Secondary server.
On the Primary Server
1 Change the Role of the server to Primary/active:
a Launch the vCenter Server Heartbeat Configure Server Wizard and click the Machine tab. In the
Active server section select Primary.
b Using the Service Control Manager, start the VMware vCenter Server Heartbeat service.
c Wait until all protected services are started.
d Using the Service Control Manager, stop the VMware vCenter Server Heartbeat service.
2 Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Server from the
list.
3 On the Database re-initialization warning page, select Do not overwrite, leave my existing database in place
option and proceed with the installation process.
4 Continue with vCenter Server installation, using the same configuration settings used for installation on
the Secondary server.
5 Once the vCenter Server upgrade process successfully completes, upgrade the existing extensions on the
server. Details for each component upgrade can be found below.
6 Verify that vCenter Server and all upgraded extensions are operational on Primary Server.
7 Using the Service Control Manager, configure VMware vCenter Server Heartbeat service Startup Type to
Automatic on both Primary and Secondary servers.
8 Start vCenter Server Heartbeat on both servers.
9 Launch the vCenter Server Heartbeat Console and connect to the server pair.
10 Verify that the Full System Check has completed and that the system replicating.
If vCenter Server fails to start on the Secondary Server following a switchover (selecting the Secondary
server icon and clicking Make Active):
1 Shutdown vCenter Server Heartbeat.
2 Launch the Configure Server wizard and set the Secondary server Role to passive.
3 Start vCenter Server Heartbeat on the Secondary server.
4 Start the Configure Server wizard on the Primary server and set the server Role to active.
5 Start vCenter Server Heartbeat on the Primary server.
6 Launch the vCenter Server Heartbeat Console and verify that the system completes the Full System
Check.
N
OTE Continuation of the upgrade process assumes the upgrade of the Secondary server completed
successfully.