vCenter High Availability (vCenter HA) protects not only against host and hardware failures but also against vCenter Server application failures. Using automated failover from active to passive, vCenter HA supports high availability with minimal downtime.

vCenter HA Deployment Options

vCenter HA protects your vCenter Server Appliance. However, Platform Services Controller provides authentication, certificate management, and licenses for the vCenter Server Appliance. As a result, you have to guarantee high availability of Platform Services Controller. You have these options.

  • Deploy an Active node with an embedded Platform Services Controller. As part of the cloning process, the Platform Services Controller and all is services are cloned as well. As part of synchronization from Active node to Passive node, Platform Services Controller on the Passive node is updated.

    When failover from the Active node to the Passive node occurs, the Platform Services Controller on the passive node are available and the complete environment is available.

  • Deploy at least two Platform Services Controller instances and place them behind a load balancer.

    When failover from the Active node to the Passive node occurs, the Passive node continues to point to the load balancer. When one of the Platform Services Controller instances becomes unavailable, the load balancer directs requests to the second Platform Services Controller instance.

See vCenter HA Deployment Options.

vCenter HA Configuration Options

You configure vCenter HA from the vSphere Web Client. The configuration wizard provides these options.

Option

Description

Basic

The Basic option clones the Active node to the Passive node and witness node, and configures the nodes for you.

If your environment meets one the following requirements, you can use this option.

  • Either the vCenter Server Appliance that becomes the Active node is managing its own ESXi host and its own virtual machine. This configuration is sometimes called a self-managed vCenter Server.

  • Or the vCenter Server Appliance managed by another vCenter Server (management vCenter Server) and both vCenter Server instances are in the same vCenter Single Sign-On domain. That means they both use an external Platform Services Controller and both are running vSphere 6.5.

See Configure vCenter HA With the Basic Option.

Advanced

The Advanced option offers more flexibility. You can use this option provided that your environment meets hardware and software requirements.

If you select this option, you are responsible for cloning the Active node to the Passive node and the Witness node. You must also perform some networking configuration.

See Configure vCenter HA With the Advanced Option.