Installation guide

QuickStart Guide
8 VMware, Inc.
Installation Prerequisites
Before starting the installation process, ensure that your server(s) and environment meet the following
prerequisites.
Installation Process
vCenter Server Heartbeat is a versatile solution that provides complete protection for vCenter Server and SQL
Server and although vCenter Server Heartbeat can be deployed in multiple configurations, this guide focuses
on installation of vCenter Server Heartbeat using the most common deployment options.For other supported
configurations, see the vCenter Server Heartbeat Installation Guide.
Table 1-1. Pre-Installation Checklist
Checked Description of Items to be Checked
o
Verify that the server is not configured as a domain controller, global catalog sever, or DNS server and that there
are no other business critical applications running on the server.
o
Verify that the Primary server is a member of the domain. The Domain for the Primary server will not change
throughout the installation process although the Primary and Secondary server names will be changed as part
of the installation procedure.
o
Verify that the Operating System is Windows 2008 or later and that all current Microsoft security updates have
been applied. If .Net 2.0 SP2 is not installed vCenter Server Heartbeat will install it during the installation
process.
o
Verify that vCenter Server 4.1 or later is installed. vCenter Server Heartbeat supports protection of both
standalone instances and also when in Linked Mode groups.
o
Verify that vCenter Guided Consolidation, vCenter Update Manager, and vCenter Converter are configured
using Fully Qualified Domain Names (FQDN) if installed.
o
Verify that the server has 2GB of RAM minimum (Recommended 4GB) in addition to any other memory
requirements for the Operating System or vCenter Server.
o
Verify that the server has at least 2GB of available disk space on the drive where vCenter Server Heartbeat will
be installed.
o
Verify that the user is logged into the domain and that the account used to perform the installation has local
administrator rights.
o
All applications to be protected are installed and configured on the server.
o
Reserve 3 public IP addresses (1 for Principal and 2 for Managed IPs) and 2 private IPs for the VMware Channel
(1 for each server). The Management IP address is unique for each server in the in the pair and should be
adjacent to the Principal (Public) IP address.
o
Verify that the Managed IP setting in the Virtual Infrastructure Client is the same IP address used for the
vCenter Server Heartbeat Principal (Public) IP address.
o
Verify that all VMware components are bound to the Principal (Public) IP address on the Principal (Public)
network adapter.
o
If installing with vCenter Server and SQL Server on the same host, verify that vCenter Server and SQL Server
are installed on separate disk drives.
o
Verify the Primary server’s Principal (Public) NIC is configured with a static IP address, correct network mask,
correct gateway IP address, correct preferred and secondary (if applicable) DNS server address
o
Verify the Primary server’s VMware Channel NIC is configured with a static IP address in a different subnet
than the Principal (Public) network, correct network mask, no gateway IP address, no DNS server IP address,
and NetBIOS is enabled (disabled by setup during the installation process).
o
Verify that all firewalls have been configured to allow traffic on both the Client Connection port (52267) which
should be configured by process and the specific Default Channel port (
57348).
o
Verify that Windows Server Backup Feature and Command Line Tools have been installed on the Primary
server prior to cloning. Installation of Windows Server Backup Feature and Command Line Tools will also
install Windows PowerShell.