This article is part of an Essential Guide, our editor-selected collection of our best articles, videos and other content on this topic. Explore more in this guide:
7. - Key terms for backup and virtual recovery: Read more in this section
Explore other sections in this guide:
- 1. - The best approaches for virtual machine backup and virtual recovery
- 2. - Using snapshots to defend and resurrect your virtual machines
- 3. - Switch virtual recovery efforts to autopilot with vCenter Site Recovery Manager
vCSHB creates a clone of both the vCenter Server and the SQL server, and then keeps both the primary and secondary vCenter Servers in sync through continuous asynchronous replication. Administrators can use vCSHB in a virtual configuration, physical configuration or a hybrid model.
vCSHB can be configured to work solely on a private LAN or stretched across two sites in "DR Mode;" the latter allows administrators to use different IP ranges, and have a user account send DNS updates in the event of failover, redirecting users and services to a functioning vCenter Server.
The primary and secondary vCenter Servers each have two NICs: The first handles the primary incoming traffic (Principal Public Network) from the vSphere Client, and the second handles replication and the "heartbeat" signal, referred to as the "VMware Channel." Administrators can also configure vCSHB to monitor and trigger remediation tasks associated with degraded performance issues.
With vCSHB, in contrast to traditional high availability (HA), administrators do not have to manage shared volumes or quorums. All activity takes place inside the guest operating system, helping administrators avoid conflicts with vMotion, VMware HA or Distributed Resource Scheduler that can result from traditional clustering.
See also: Heartbeat