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 Launch vCenter Server Heartbeat Console.
10 Perform a manual failover using vCenter Server Heartbeat Console to make the Secondary node active.
Note, at this point users may notice a slight interruption to the protected application.
11 When the failover is complete, launch Windows Update on the Primary (passive) node.
12 Download and install patches or hotfixes, but DO NOT reboot the node if instructed to do so.
13 Shutdown vCenter Server Heartbeat selecting the option to Shutdown vCenter Server Heartbeat, but leave
protected applications running.
14 Reboot the Primary node if prompted at step 13 to complete installation of OS patches or hotfixes.
15 Verify all patches or hotfixes are installed properly.
16 On the Primary (passive) node, launch Windows Update again and check for any further updates that may
be required. If additional updates are required, repeat Steps 11 to 15.
17 Start vCenter Server Heartbeat on the Secondary node and also on the Primary node if no reboot was
required at step 14 allowing the nodes to synchronize.
18 Launch vCenter Server Heartbeat Console.
19 Perform a manual failover using the vCenter Server Heartbeat Console to make the Primary node active
again. Note, at this point users may notice a slight interruption to the protected application.
Applying SQL Server Patches
Prior to upgrading SQL Server with vCenter Server Heartbeat installed, check with VMware for the latest version
of vCenter Server Heartbeat and verify that it supports the new application version or Service Pack.
To upgrade SQL Server with vCenter Server Heartbeat installed:
Prerequisites
Prior to attempting this upgrade, read the entire procedure.
Procedure
1 If the Primary server is active, use vCenter Server Heartbeat Console on the Secondary server to perform
a failover to make the Secondary server active. If the Secondary server is currently active, go to Step 2.
2 Shutdown vCenter Server Heartbeat on both the Primary and Secondary servers, leaving the protected
applications running on Secondary (active) server.
3 Using the Service Control Manager, configure VMware vCenter Server Heartbeat service Startup Type to
Manual on both Primary and Secondary servers.
Upgrade starts on the Secondary (active) server.
4 Upgrade the SQL Server or apply the Service Pack to the Secondary (active) server by running Setup.exe
5 Restart the Secondary server if requested.
■
The SQL Server starts
■
The SQL Server upgrade / Service Pack resumes
6 Allow the SQL Server upgrade/Service Pack to complete.
7 Once complete, start SQL Server services.
8 Verify that SQL Server is operational.
VMware, Inc. 77
Chapter 4 Maintaining vCenter Server Heartbeat