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
On the Secondary Server
Procedure
1 Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Server from the
list.
Note Before proceeding with the database upgrade, perform a backup of the database.
2 When asked, select Do not overwrite, leave the existing database in place.
3 Continue with vCenter Server installation and record all conguration settings used.
Note On the VMware vCenter Server service account information page, VMware recommends providing
the same credentials used for the current service (open the Service Control Manager and check the Logon
As Account for VMware VirtualCenter Server service).
4 Once the vCenter Server upgrade process successfully completes, upgrade the existing extensions on the
server.
5 If asked, do not reboot the server.
6 Verify that vCenter Server and all upgraded extensions are operational.
If the Upgrade on the Secondary Fails, research the cause of the upgrade failure. If the issue can be resolved
then it is safe to proceed with upgrade procedure. Otherwise, go to “If the Upgrade on the Secondary
Server Fails,” on page 38.
7 Change the Role of the server to Secondary/passive:
a Launch the vCenter Server Heartbeat Congure Server wizard and click the Machine tab. In the Active
server section select Primary.
b Reboot Secondary server.
If the Upgrade on the Secondary Server Fails
If the upgrade on the Secondary server fails and the issue cannot be resolved, revert to a previous version.
Procedure
1 Uninstall the upgraded components.
2 On the Secondary server, launch the vCenter Server Heartbeat Congure Server wizard and click the
Machine tab. In the Active server section select Primary.
3 Reboot the server. vCenter Server Heartbeat starts and vCenter Server is stopped.
4 On the Primary server, launch the vCenter Server Heartbeat Congure Server wizard and click the Machine
tab. In the Active server section select Primary.
5 Restart vCenter Server Heartbeat on the Primary Server and allow the system to synchronize.
6 Start the vCenter Server Heartbeat Console and verify that the system completes the Full System Check.
On the Primary Server
Note Continuation of the upgrade process assumes the upgrade of the Secondary server completed successfully.
38 VMware, Inc.
Administrator Guide