Specifications
Table Of Contents
- Reference Guide
- Contents
- About This Book
- Getting Started
- Installation
- vCenter Server Heartbeat Implementation
- vCenter Server Heartbeat Installation on Windows Server 2003
- vCenter Server Heartbeat Installation on Windows Server 2008
- Configuring vCenter Server Heartbeat
- Server Configuration Wizard
- Configuring the Machine Identity
- Configuring the Server Role
- Configuring the Client Connection Port
- Configuring Channel IP Routing
- Configuring the Default Channel Port
- Configuring Low Bandwidth Module
- Configuring Public IP Addressing
- Enabling Network Monitoring
- Configuring Split-Brain Avoidance
- Managing vCenter Server Heartbeat License Keys
- Configuring Message Queue Logs
- Configuring the Maximum Disk Usage
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Status and Control
- Performance Protection
- Data Protection
- Data Protection Overview
- Other Administrative Tasks
- Troubleshooting
- Troubleshooting Unexpected Behaviors
- Two Active Servers
- Two Passive Servers
- Synchronization Failures
- Registry Status is Out of Sync
- Channel Drops
- Subnet or Routing Issues
- MaxDiskUsage Errors
- MaxDiskUsage Error Messages
- [L9]Exceeded the Maximum Disk Usage (VCChannelExceededMaxDiskUsageException)
- [L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
- [L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
- [L20]Out of Disk Space (VCChannelOutOfDiskSpaceException)
- Application Slowdown
- Poor Application Performance
- Both Servers Can Accommodate the Initial Load but the Load Has Increased
- One Server Can Provide Adequate Resource Support, but the Other Cannot
- Scheduled Resource Intensive Tasks
- Appendix - Setup Error Messages
- Glossary
Reference Guide
64 VMware, Inc.
29 Before starting vCenter Server Heartbeat, verify the time synchronization between the Primary and
Secondary servers. When a difference exists, synchronize the Secondary (passive) server to the Primary
(active) server across the VMware Channel. Type the following command at the command prompt:
net time \\<Primary_Channel_IP_address> /set
Start vCenter Server Heartbeat on the Primary server. Right-click the vCenter Server Heartbeat System
Tray icon and select Start VMware vCenter Server Heartbeat. The icons change from a double dash to a
P indicating the server is the Primary server, and an A indicating the server is acting in an active role.
30 The Primary and Secondary servers establish a handshake and commence replication.
If vCenter Server only was installed and you want to install a separate SQL Server, repeat the installation
process for the Primary and Secondary server at the remote site and selecting SQL Server only.
To install the SQL Server on a separate host from the vCenter Server, go to “Primary Server” on page 32.
31 Configure the appropriate username and password in the vCenter Server Heartbeat Console:
a Start vCenter Server Heartbeat Console from the desktop shortcut or Start > All Programs > VMware
> VMware vCenter Server Heartbeat > Manage Server. The login window appears.
b Before you log in, you must identify the pair of servers to administer. Click Servers.
cClick Add Pair.
N
OTE The installation is complete if vCenter Server was installed with a local SQL Server or only vCenter
Server was installed with no separate SQL Server.
N
OTE Add the Principal (Public) IP address or FQDN of the Primary server to ensure that you can
administer the server pairs from the vCenter Server Heartbeat Console regardless of the role (active
or passive) of the current server.