6.3
Table Of Contents
- Installation Guide
- Contents
- About This Book
- Getting Started
- Installation
- vCenter Server Heartbeat Implementation
- Installing vCenter Server Heartbeat on Identical Nodes
- Installing vCenter Server Heartbeat on Non-Identical Nodes
- 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 23
“Cloning Technology Options” on page 24
“Application Component Options” on page 25
“Network Options” on page 26
“Antivirus Recommendations” on page 29
“Deployment Options Summary” on page 29
Overview
vCenter Server Heartbeat is a versatile solution that provides 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 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.
vCenter Server Heartbeat
Implementation
2
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.