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. 21
2
This chapter includes the following topics:
“Overview” on page 21
“Environmental Prerequisites” on page 21
“Common Requirements” on page 22
“Server Architecture Options” on page 22
“Cloning Technology Options” on page 24
“Application Component Options” on page 25
“Network Options” on page 25
“Antivirus Recommendations” on page 27
“Deployment Options Summary” on page 28
Overview
vCenter Server Heartbeat is a versatile solution that provides you with complete protection of vCenter Server
and SQL Server. It can be deployed in a LAN for high availability or across a WAN to provide disaster recovery.
vCenter Server Heartbeat can protect vCenter Server and SQL Server installed on the same server, or protect
vCenter Server and SQL Server on separate servers. This flexibility enables vCenter Server Heartbeat to protect
vCenter Server when using remote databases other than SQL Server.
This chapter discusses the deployment options and prerequisites necessary to successfully implement vCenter
Server Heartbeat and provides a step by step process to assist in selecting options required for installation. The
deployment scenario table provides a visual reference to configuration options supported by vCenter Server
Heartbeat.
During the installation process, vCenter Server Heartbeat performs a variety of checks to ensure the server
meets the minimum requirements for a successful installation. A critical stop or warning message appears if
the server fails a check. Refer to the Appendix – Setup Error Messages in this guide for a list of the checks and
an explanation of the message. You must resolve critical stops before you can proceed with setup.
Prior to installing vCenter Server Heartbeat, select the deployment options you intend to use. The installation
process prompts you to select options throughout the procedure to create the configuration you want.
Environmental Prerequisites
vCenter Server Heartbeat cannot protect a server configured with the following roles: domain controller,
global catalog, or DNS. Please note, because vCenter Server Heartbeat only protects the vCenter Server and
SQL Server applications, no other critical business applications should be installed on the server.
vCenter Server Heartbeat
Implementation
2