Specifications
Table Of Contents
- Reference Guide
- Contents
- About This Book
- Getting Started
- Installation
- vCenter Server Heartbeat Implementation
- vCenter Server Heartbeat Installation on Windows Server 2003
- vCenter Server Heartbeat Installation on Windows Server 2008
- Configuring vCenter Server Heartbeat
- Server Configuration Wizard
- Configuring the Machine Identity
- Configuring the Server Role
- Configuring the Client Connection Port
- Configuring Channel IP Routing
- Configuring the Default Channel Port
- Configuring Low Bandwidth Module
- Configuring Public IP Addressing
- Enabling Network Monitoring
- Configuring Split-Brain Avoidance
- Managing vCenter Server Heartbeat License Keys
- Configuring Message Queue Logs
- Configuring the Maximum Disk Usage
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Status and Control
- Performance Protection
- Data Protection
- Data Protection Overview
- Other Administrative Tasks
- Troubleshooting
- Troubleshooting Unexpected Behaviors
- Two Active Servers
- Two Passive Servers
- Synchronization Failures
- Registry Status is Out of Sync
- Channel Drops
- Subnet or Routing Issues
- MaxDiskUsage Errors
- MaxDiskUsage Error Messages
- [L9]Exceeded the Maximum Disk Usage (VCChannelExceededMaxDiskUsageException)
- [L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
- [L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
- [L20]Out of Disk Space (VCChannelOutOfDiskSpaceException)
- Application Slowdown
- Poor Application Performance
- Both Servers Can Accommodate the Initial Load but the Load Has Increased
- One Server Can Provide Adequate Resource Support, but the Other Cannot
- Scheduled Resource Intensive Tasks
- Appendix - Setup Error Messages
- Glossary
VMware, Inc. 23
Chapter 2 vCenter Server Heartbeat Implementation
The Secondary virtual machine must meet the minimum requirements.
The specifications of the Secondary virtual machine must match the specifications of the Primary virtual
machine as follows:
Similar CPU (including resource management settings)
Memory configuration (including resource management settings)
Appropriate resource pool priorities
Each virtual machine used in the V2V pair must be on a separate ESX host to guard against failure at the
host level.
Each virtual NIC must use a separate virtual switch.
Physical to Virtual (P2V)
P2V architecture is used when the environment requires a mix of physical and virtual machines, such as when
vCenter Server is installed on a physical server in an environment where available hardware is limited. This
architecture is appropriate if you must avoid adding more physical servers or if you plan to migrate to virtual
technologies over a period of time. With P2V architecture, you can test vCenter Server running in a virtual
environment or migrate from Physical to Virtual without any downtime. The Secondary virtual machine must
meet the minimum requirements.
The specifications of the Secondary virtual machine must match the Primary physical server as follows:
Similar CPU
Identical Memory
The Secondary virtual machine must have sufficient priority in resource management settings so that
other virtual machines do not impact its performance.
Each virtual NIC must use a separate virtual switch.
Physical to Physical (P2P)
P2P architecture is used in environments where both the Primary and Secondary servers are physical servers.
Use of P2P limits installation options as it requires use of the Install Clone technique. This architecture requires
attention to detail when preparing for installation as both hardware and software must meet specific
prerequisites.
Primary Server
The Primary server must meet the following requirements:
Hardware as specified in “Common Requirements” on page 22.
Software as specified in “Common Requirements” on page 22.