VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1 Specifications Page 25

  • Download
  • Add to my manuals
  • Print
  • Page
    / 204
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 24
VMware, Inc. 25
Chapter 2 vCenter Server Heartbeat Implementation
Application Component Options
vCenter Server Heartbeat can accommodate any of the supported vCenter Server configurations and protects
the following components:
VirtualCenter Server Version 2.5
VMware VirtualCenter Server
VMware Capacity Planner
VMware Converter Enterprise
VMware Update Manager
VMware License Server
vCenter Server Version 4.0
VMware vCenter Server
VMware Guided Consolidation Service
VMware License Sever
VMware ADAM
VMware vCenter Management Web Server
VMware Update Manager
VMware Converter Enterprise
Guided Consolidation Service
VMware Orchestrator
VMware vSphere Host Update Utility
vCenter Server with SQL Server on the Same Host
To ensure adequate performance in 20+ host or 200+ virtual machine environments, VMware recommends that
SQL Server and vCenter Server be installed on separate physical disk drives. VMDKs must be on separate
datastores to avoid potential disk bottlenecks.
vCenter Server with SQL Server on a Separate Host
When installing vCenter Server Heartbeat in an environment where SQL Server is on a separate host from
vCenter Server, repeat the installation process for the Primary and Secondary server specifically for the SQL
Server.
To ensure proper failover, increase the default Heartbeat interval for the vCenter Server from 20 to 30 seconds.
vCenter Server Only
The vCenter Server Only option requires a single iteration of the installation process because the database is
not protected.
Network Options
Networking requirements are contingent on how vCenter Server Heartbeat is deployed. To deploy as a High
Availability (HA) solution, a LAN configuration is required. To deploy vCenter Server Heartbeat for Disaster
Recovery (DR), a WAN configuration is required. Each network configuration has specific configuration
requirements to ensure proper operation.
N
OTE Ensure that all VMware components are bound to the Principal (Public) IP address on the Principal
(Public) network adapter and that the Principal (Public) network adapter is listed first in the bind order of the
Network Connections > Advanced > Advanced Settings window.
Page view 24
1 2 ... 20 21 22 23 24 25 26 27 28 29 30 ... 203 204

Comments to this Manuals

No comments