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
Procedure
1 Change the Role of the server to Primary/active:
a Launch the vCenter Server Heartbeat Congure 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 conguration settings used for installation on
the Secondary server.
5 Once the vCenter Server upgrade process successfully completes, upgrade the existing extensions on the
server.
6 Verify that vCenter Server and all upgraded extensions are operational on Primary Server.
7 Using the Service Control Manager, congure 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
Procedure
1 Shutdown vCenter Server Heartbeat.
2 Launch the Congure Server wizard and set the Secondary server Role to passive.
3 Start vCenter Server Heartbeat on the Secondary server.
4 Start the Congure 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.
7 Investigate the cause of the vCenter Server failure on the Secondary server.
VMware, Inc. 39
Chapter 3 Server Protection