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
Application Slowdown
Operations performed by the application can take longer to complete, and in turn, can affect the time required
to log in to a remote client, or to open or save a file.This is true for both nodes running vCenter Server Heartbeat
and for nodes running any other application. vCenter Server Heartbeat can monitor system performance
counters and display warnings when predefined thresholds are exceeded, but it does not actively manage
system resources for other applications. Like any other application, it also requires a finite amount of resources
for its own operations in addition to the resources used by the operating system and the protected application.
The machines hosting vCenter Server Heartbeat must meet recommended hardware requirements and must
be powerful enough to support the load, the protected applications, and any other critical applications running
on the same pair.
Poor Application Performance
When applications are competing for resources, one or more applications can perform poorly.
Problem
Neither node in the pair can accommodate the load placed upon it during normal operation.
Cause
The Primary's resource usage in one or more areas reached close to the maximum before vCenter Server
Heartbeat was installed.
Solution
◆
Heartbeat Diagnostics can report these conditions and issues warnings if CPU usage or memory usage
exceed a certain percentage of the available resource. Information provided by Heartbeat Diagnostics can
minimize the risk of application slowdown by identifying needed hardware/resource upgrades on the
Primary.
Both Servers Can Accommodate the Initial Load but the Load Has Increased
Any software installed on a node consumes a finite amount of system resources when it runs and it must share
the resources it uses with any other applications running at the same time. Increased demand caused by
additional user activity can have an impact on the performance.
Problem
Increased user activity slows application response time.
Cause
The pair operates normally when vCenter Server Heartbeat is first installed, but performance decreases due
to increased user activity. For example, users on the SQL Server system increase or the typical usage pattern
becomes more intense.This can be a gradual and sustained increase over time, or transient if a specific event
triggers a temporary surge in user activity.
Solution
◆
If the situation is sporadic, it can correct itself when the load decreases. If the increase is sustained and
permanent, upgrade the hardware or allocate additional resources.
94 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide