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
VMware, Inc. 27
Chapter 2 vCenter Server Heartbeat Implementation
WAN Requirements
WAN deployments require the following:
Persistent static routing configured for the channel connection(s) where routing is required
Two NICs (1 x Public and 1 x Channel) are recommended
At least one Domain Controller at the Disaster Recovery (DR) site
If the Primary and DR site use the same subnet:
During install, follow the steps for a LAN or VLAN on the same subnet
Both servers in the vCenter Server Heartbeat pair use the same Public IP address
If the Primary and DR site use different subnets:
During install, follow the steps for a WAN
Both servers in the vCenter Server Heartbeat pair require a separate Principal (Public) IP address and
a VMware Channel IP address in a separate dedicated subnet
Provide a user account with rights to update DNS using the DNSUpdate utility provided as a
component of vCenter Server Heartbeat through vCenter Server Heartbeat Console Application >
Task > User Accounts
VMware recommends integrating Microsoft DNS into AD so that DNSUpdate can identify all DNS
Servers that require updating
At least one Domain Controller at the DR site
Refer to the following articles in the VMware Knowledge Base:
KB 1008571 – Configuring DNS in a WAN Environment
KB 1008605 – Configuring vCenter Server Heartbeat to Update BIND9 DNS Servers Deployed in a
WAN
Bandwidth
Determine the available bandwidth and estimate the required volume of data throughput to determine
acceptable latency for the throughput. Additionally, the bandwidth can affect the required queue size to
accommodate the estimated volume of data. VMware recommends making a minimum of 1Mbit of spare
bandwidth available to vCenter Server Heartbeat.
vCenter Server Heartbeat includes a Low Bandwidth Module for use in WAN environments. When enabled,
the VMware Channel compresses the data, optimizing the traffic for low bandwidth connections causing some
additional CPU load on the active server.
Latency
Latency has a direct effect on data throughput. Latency on the link should not fall below the standard defined
for a T1 connection.
Heartbeat Diagnostics can assist in determining the available bandwidth, required bandwidth, and server
workload. For more information about Heartbeat Diagnostics, contact VMware Professional Services.
Antivirus Recommendations
Consult with and implement the advice of your antivirus (AV) provider, as VMware guidelines often follow
these recommendations. Consult the VMware knowledge base for up to date information on specific AV
products.
Do not use file level AV to protect application server databases, such as MS SQL Server databases. The nature
of database contents can cause false positives in virus detection, leading to failed database applications, data
integrity errors, and performance degradation.