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
1Introduction
This chapter includes the following topics:
■
“vCenter Server Heartbeat Concepts,” on page 7
■
“vCenter Server Heartbeat Protection,” on page 9
■
“vCenter Server Heartbeat Communications,” on page 12
■
“vCenter Server Heartbeat Failover Processes,” on page 14
vCenter Server Heartbeat Concepts
vCenter Server Heartbeat is a Windows based service specifically designed to provide High Availability (HA)
or Disaster Recovery (DR) protection for vCenter Server configurations.
Architecture Overview
vCenter Server Heartbeat is deployed in an “Active–Passive” architecture enabling configuration for either
“High Availability (HA)” in a Local Area Network (LAN)/Metropolitan Area Network (MAN) or “Disaster Recovery
(DR)” in a Wide Area Network (WAN) for vCenter Server, View Composer and/or SQL Server.
Server Identity
vCenter Server Heartbeat software is installed on an existing production server instance (virtual or physical)
known as the “Primary” node which runs the protected applications (vCenter Server, View and/or SQL Server).
An additional server instance (virtual or physical), known as the “Secondary” node, operates as a ready standby
to provide service in the event of an application, system, or hardware failure.The terms Primary and Secondary
refer to the “Identity” of each node and do not change over the life of the node.
Active / Passive Roles
The “Role” of a node describes what the node is currently doing.
■
Active Node – If the node is currently running protected applications, the node is said to be “Active”. The
active node will always host the running instance of protected applications. Only one node can be active
at any one time.
■
Passive Node – The “Passive” node acts as the ready standby for the active node. Protected applications
are not running on the passive node.
VMware, Inc. 7