1. Introduction
Vcenter Server heartbeat provides mission-critical high availability for VMware vcenter Server, protecting your virtual infrastructure from hardware, network, configuration, and more, Windows-based services for VCenter The server configuration provides high-availability protection without the need for dedicated hardware. VCenter Server Heartbeat is based on a pair of cloned
The active/passive server runs, which means that two computers are identical, including the computer name, domain identity, IP address, and so on. Because Vcenter Server heartbeat is software-based, it can be implemented in a physical or virtual environment, supporting virtual-to-virtual (V2V), physical-to-virtual (P2V), physical-to-physical (peer-to) configuration, and hardware-independent.
The default failover mode is automatic, which can be switched automatically on a virtual machine or on a physical machine.
2. Precautions
The following points need to be considered when implementing Vcenter Server Heartbeat:
<1> needs another network link for replication and heartbeat between the two servers.
<2> If another vcenter server is in a co-site, make sure there is enough network connectivity between the sites
<3> currently supports only 32-bit SQL Server 2005/2008 installed on the X64 operating system
<4> cannot be with controllers, global catalog servers, and DNS servers.
3. Virtual machine to virtual machine
Advantages:
<1> Reduce hardware costs
<2> Shorten installation time
<3> install using "Pre-cloning" technology
4. Physical to Virtual
Advantages:
<1> suitable for hybrid environments where both physical and virtual machines must be used
<2> for situations where you don't want to add more physical servers or plan to migrate to virtual technology
<3> requires a similar CPU, the same memory, and a resource reorganization of the secondary virtual machine.
VCenter Server Heartbeat