To ensure Platform Services Controller high availability in external deployments, you must install or deploy at least two joined Platform Services Controller instances in your vCenter Single Sign-On domain. When you use a third-party load balancer, you can ensure an automatic failover without downtime.

Example of a Load Balanced Pair of Platform Services Controller Instances
Two joined Platform Services Controller instances connected to a load balancer and two vCenter Server instnaces connected to the same load balancer.

You can use a third-party load balancer per site to configure Platform Services Controller high availability with automatic failover for this site. For information about the maximum number of Platform Services Controller instances behind a load balancer, see the Configuration Maximums documentation.

Important

To configure Platform Services Controller high availability behind a load balancer, the Platform Services Controller instances must be of the same operating system type. Mixed operating systems Platform Services Controller instances behind a load balancer are unsupported.

The vCenter Server instances are connected to the load balancer. When a Platform Services Controller instance stops responding, the load balancer automatically distributes the load among the other functional Platform Services Controller instances without downtime.

Example of Two Load Balanced Pairs of Platform Services Controller Instances Across Two Sites
Two joined pairs of Platform Services Controller instances, each pair is in a separate site, each pair is connecteed to a load balancer, and two vCenter Server instances are connected to each load blancer.

Your vCenter Single Sign-on domain might span multiple sites. To ensure Platform Services Controller high availability with automatic failover throughout the domain, you must configure a separate load balancer in each site.

Example of Two Joined Platform Services Controller Instances with No a Load Balancer
Two joined Platform Services Controller instances with two vCenter Server instnaces connected to each Platform Services Controller.

When you join two or more Platform Services Controller instances in the same site with no load balancer, you configure Platform Services Controller high availability with a manual failover for this site.

Note

If your vCenter Single Sign-On domain includes three or more Platform Services Controller instances, to ensure Platform Services Controller reliability when one of the instances fails, you can manually create a ring topology. To create a ring topology, use the /usr/lib/vmware-vmdir/bin/vdcrepadmin -f createagreement command against the first and last Platform Services Controller instance that you have deployed.

Example of Two Joined Pairs of Platform Services Controller Instances Across Two Sites with No Load Balancer
Two joined pairs of Platform Services Controller instances, each pair is in a separate site, and each pair is connecteed to a vCenter Server instance.
Important

Repointing vCenter Server between sites and domains is unsupported. If no functional Platform Services Controller instance is available in the site, you must deploy or install a new Platform Services Controller instance in this site as a replication partner of a functional Platform Services Controller instance from another site.