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
5 Restart the Primary node and reconnect or enable the NIC.
6 After restart, check that the Taskbar icon now reflects the changes and displays P / – (Primary and passive).
7 On the Secondary active node or from a remote client, launch vCenter Server Heartbeat Console and
confirm that the Secondary node is reporting as active.
If the Secondary is not displaying as active, perform the following steps:
a If the vCenter Server Heartbeat Console is unable to connect remotely, try running it locally. If you
are still unable to connect locally, use the Service Control Manager (SCM) to verify that the service
is running. If the service is not running, review the event logs for a cause.
b Run the Configure Server wizard and confirm that the node identity is set to Secondary and that the
Active Server is set to Secondary.
Note If vCenter Server Heartbeat is running, you can run the Configure Server wizard but any
changes made will not be saved.
c Verify that the protected application is accessible from clients. If accessible, start vCenter Server
Heartbeat on the Secondary. If the application is not accessible, review the application logs to determine
why the application is not running.
d Start vCenter Server Heartbeat on the Secondary active node.
Note At this point, the data on the Secondary (active) node should be the most up to date and this node
should be the live node on your network. When vCenter Server Heartbeat starts, it overwrites all the
protected data (configured in the File Filter list) on the Primary (passive) node. If you are not sure that the
data on the active node is the most current and up to date, contact VMware Support
(www.vmware.com/support). Go on to the next step only if you are sure that you want to overwrite the
protected data on the passive node.
8 Start vCenter Server Heartbeat on the Secondary (active) node and check that the Taskbar icon now
reflects the correct status by showing S / A (Secondary and active).
Managing Application Protection
vCenter Server Heartbeat incorporates an Application Management Framework (AMFx) to manage vCenter
Server Heartbeat plug-ins.
The AMFx provides additional functions while maintaining the traditional stability of VMware software. Use the
AMFx to install and remove plug-ins on the fly while vCenter Server Heartbeat continues to provide protection
to currently installed applications.
The AMFx also employs sponsorship for protected application files and services. With sponsorship, multiple
plug-ins can share files or services.When removing a plug-in, sponsorship prevents removal of a shared file
or service that is still required by a remaining plug-in.
vCenter Server Heartbeat uses the System plug-in to monitor the node's performance.With the System plug-in,
you can configure a variety of counters and assign actions when associated rules are exceeded.
VMware, Inc. 53
Chapter 3 Managing vCenter Server Heartbeat