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
Installation Guide
36 VMware, Inc.
23 The vCenter Server Heartbeat server pair can be administered remotely on client machines using the
vCenter Server Heartbeat Console. The vCenter Server Heartbeat Console connects to an IP address of the
active server using the default client connection port of 52267. If this port is already in use, type an
available client connection port in the text box. Click Next.
24 Select the applications to protect. All licensed vCenter Server Heartbeat features are listed.
If installing vCenter Server only, or vCenter Server locally and the SQL Server on a separate server,
select Protect Virtual Center only.
If installing SQL Server remotely, upon completion of the vCenter Server installation locally, repeat
the installation procedure at the remote SQL Server location and select Protect SQL Server only.
If installing both vCenter Server and SQL Server locally, select Protect Virtual Center and SQL
Server.
If View Composer is installed, select the View Composer check box to provide protection for View
Composer.
25 To facilitate the clone of the Primary server onto the Secondary server, you must back up pertinent
components of the Primary server for restoration on to the Secondary server. Where VMware Channel
communications are fast and reliable, for instance in a LAN topology, you can directly create the backup
files over the VMware Channel connections to a partition on the Secondary server.
Where the VMware Channel connection is slower than 10 Mbit/s or risks an interruption in connection,
for example in a WAN topology, save the backup file locally and manually port the file to the Secondary
server.
Microsoft Windows Backup Configuration options. Including the applications’ protected data greatly
increases the backup file size and therefore increases the time of the backup operation. Due to the
potential large size of the backup file, careful consideration is required when including application data
and specifying the backup folder location.
Depending on the network topology between the servers, backup files can include or exclude application
data. Including application data in the backup file decreases the time to initially verify and synchronize
the applications data on first start up of vCenter Server Heartbeat. This is useful where VMware Channel
connections are slower than LAN speed, such as in a WAN implementation.
To estimate the maximum size of the backup file, add together the size of each volume that contains
system data and application data. Although the actual size of the backup file can be smaller, using this
rule of thumb helps ensure a successful installation.
You have the following options:
For installation on Windows Server 2003 using the Pre-Clone technique, go to Step 26 on page 37.
For installation on Windows Server 2003 using the Install Clone technique, continue with Step a of
Step 25.
For installation on Windows Server 2008 using the Pre-Clone technique, go to Step d of Step 26
For installation on Windows Server 2008 using the Install Clone technique, go to Step Step d of
Step 25.
Continue with Step a.
a To perform a direct backup, click Map Network Drive and specify a network mapping to the
Secondary server. Type in the path or Browse to the location to receive the backup file.
b Select an appropriate drive letter for the mapping and specify the required share on the Secondary
server using the channel address of the Secondary server as the server name, for example:
\\10.0.0.6\Backup. Verify that the mapped partition has enough free space, a minimum of 2GB,
to accommodate the backup file.