Search the VMware Knowledge Base (KB)
View by Article ID

vCenter Server Heartbeat Installation Prerequisites (1017587)

  • 4 Ratings

Symptoms

This article describes the hardware and software prerequisites for installing vCenter Server Heartbeat.

Resolution

Before You Begin

The server to be protected by vCenter Server Heartbeat cannot be configured as a domain controller, global catalog, DHCP or DNS server. These roles and services must be removed before proceeding with installation.

Hardware Requirements

Primary Server

  • Must meet Microsoft's requirements for one of the following installed operating systems:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
  • 1 GB RAM minimum, 2 GB RAM recommended
  • 256 MB of available RAM minimum
  • 2 GB of available hard disk space
  • 2 non-teamed NICs required, 3 non-teamed NICs recommended
  • Multiple hard disk drives are recommended as per application vendors' requirements. Avoid locating OS, database, and log files on the same disks

Secondary Server

  • Must meet Microsoft's requirements for one of the following installed operating systems:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
  • 1 GB RAM minimum, 2 GB RAM recommended 
  • 256 MB of available RAM minimum
  • Total hard disk space should be greater than or equal to the Primary Server
  • Same number of NICs as the Primary Server
  • Hard drive lettering scheme must match the Primary Server (although underlying hardware may be different)

Software Requirements

Primary Server

  • Installed operating system:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
      or
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
  • Latest Microsoft security updates
  • Installation of vCenter Server Heartbeat requires local admin rights

Secondary Server

  • OS version, service pack version and security updates must match the Primary Server
  • OS must be installed to same drive letter and directory as the Primary Server
  • ACPI compliance must match the Primary Server
  • Different machine name from the Primary Server
  • Setup in a workgroup
  • The same Windows IIS components must be installed as the Primary Server. Once installed, set each of these component services to have the same startup type as the Primary Server (automatic, manual or disabled)
  • System date/time and time zone consistent with Primary Server
  • Additional applications, including the protected application (such as SQL) must NOT be installed on the Secondary Server

Networking Configuration

Primary Server

Public Network connection(s) configured with:
  • Static IP address
  • Correct network mask
  • Correct gateway address
  • Correct DNS server addresses

Channel Network connection(s) configured with:

  • Static IP address (in a different subnet from the Public Network)
  • Correct network mask
  • No gateway IP address
  • No DNS server addresses
  • In a LAN environment, a cross-over cable should be used to connect the channel connection(s) on the Primary Server to the channel connection(s) on the Secondary Server
  • In a WAN environment, persistent static route(s) must be configured to the channel connection(s) on the Secondary Server

Secondary Server

Channel Network connection(s) configured with:

  • Static IP address (in a different subnet from the Public Network)
  • Correct network mask
  • No gateway IP address
  • No DNS server addresses
  • File and Print Sharing enabled
  • In a WAN environment, persistent static route(s) must be configured to the channel connection(s) on the Primary Server. See Creating a static route for the VMware Channel (1023026).
  • Connection in a WAN environment.

Login Account Privilege Requirements

Administrator privileges required for login accounts vary according to configuration:
  • For installation and normal system administration, a login account with Local Administrator privilege must be used. This account may also be a Domain Administrator if login with cached credentials is permitted by the security policy.
  • For installation of a Secondary or Tertiary server which is not already a clone of the Primary server, a Local Administrator account is required for installation.
  • For WAN installations, where the public IP addresses differ between servers, the administrator account used must additionally be a member of the DNSadmin group. Domain Administrator accounts have sufficient privilege to meet this requirement.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 4 Ratings
Actions
KB: