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
9 Change the server role to Secondary/passive.
a Launch the vCenter Server Heartbeat Configure Server wizard and select the Machine tab.
b In the Active Server section, change the server role for the Primary server to Active and click Finish.
10 Start VMware vCenter Server Heartbeat on the Secondary server only.
11 Restart the Secondary server.
12 The upgrade process continues on the Primary (passive) server.
Important Use identical Setup program upgrade parameters on both the Primary and Secondary servers.
13 Change the server role to Primary/active:
a Launch the vCenter Server Heartbeat Configure Server wizard and select the Machine tab.
b Change the server role for the current (Primary) server to Active and click Finish.
c Using the Service Control Manager, start the VMware vCenter Server Heartbeat service.
d Using the vCenter Server Heartbeat Console, verify that all status icons on the Server: Summary
page are green indicating that the Start process has completed.
e Using the Service Control Manager, stop the VMware vCenter Server Heartbeat service.
14 Upgrade SQL Server on the Primary (active) server by running Setup.exe
15 Restart the Primary server if required.
■
The server returns as passive with vCenter Server Heartbeat in the stated state
■
The SQL Server services stop
■
The SQL Server upgrade resumes
16 If server was restarted in Step 15, allow the SQL Server upgrade to complete.
17 Verify that vCenter Server and all updated extensions are operational.
18 Finalize the installation and synchronize vCenter Server Heartbeat:
a Using the Service Control Manager, configure VMware vCenter Server Heartbeat service Startup
Type to Automatic on both Primary and Secondary servers.
b Start vCenter Server Heartbeat on both servers.
c Launch the vCenter Server Heartbeat Console and connect to the server pair.
d Verify that the system completes the Full System Check and is replicating.
e Using the vCenter Server Heartbeat Console, navigate to the Application:Tasks page and manually
run the Protected Service Discovery task.
Shutting Down Windows
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 Windows Shutdown confirmation message is displayed, click Cancel and stop vCenter Server
Heartbeat before attempting Windows shut down again.
78 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide