6.3

Installation Guide
60 VMware, Inc.
Post Installation Configuration
Upon completion of installation, a series of tasks must be performed to ensure that vCenter Server Heartbeat
is properly configured.
1 When protecting SQL Server, verify that the SetSPN.exe tool present on both the Primary and the
Secondary servers at the following locations:
 On Windows Server 2003 environments, in Program Files\Support Tools. If Support Tools are
not installed on your system, download them from http://support.microsoft.com/?kbid=926027 and
copy SetSPN.exe to <install_path>\R2\bin.
 On Windows Server 2008 environments, in Windows\System32. This is normally present as a
component of the Windows 2008 operating system.
SetSPN.exe is a Microsoft command-line tool that reads, modifies, or deletes the Service Principal Names
(SPN) directory property for an Active Directory service account and is required to be present on both
servers prior to starting vCenter Server Heartbeat for the first time.
2 Start vCenter Server Heartbeat on the Primary server. Right-click the vCenter Server Heartbeat System
Tray icon and select Start VMware vCenter Server Heartbeat. The icons change from a double dash to a
P, indicating the server is the Primary server, and an A indicating the server is acting in an active role.
3 Start vCenter Server Heartbeat on the Secondary server. Right-click the vCenter Server Heartbeat System
Tray icon and select Start VMware vCenter Server Heartbeat. The icon changes from a double dash to an
S, indicating that the server is the Secondary server, and a dash (–), indicating that the server is in a
passive role.
The Primary and Secondary servers establish a handshake and commence replication.
4 Verify that Nslookup resolves as shown below:
 Nslookup resolves Service Name to Public IP
 Nslookup resolves Primary Name to Public IP
 Nslookup resolves Secondary Name to Secondary Passive IP
If vCenter Server only was installed and you want to install a separate SQL Server, repeat the installation
process for the Primary and Secondary servers at the remote site and select Protect SQL Server Only.
5 To install vCenter Server Heartbeat on SQL Server when installed on a separate host from the vCenter
Server, go to “Primary Server” on page 32
Configuring VirtualCenter Plug-in with the Correct Credentials
After installation is complete, you must enter the credentials for an account with rights to the Virtual
Infrastructure.
To add the Virtual Infrastructure credentials
1 Navigate to the Applications: Plug-ins page.
2 Select the VirtualCenter Plug-in.
3Click Edit.
4 Type the Username and Password for an account with rights to the Virtual Infrastructure.
5Click OK.