4.6.2 Multi-Site
Each availability zone (site) has a shared Platform Services Controller node with a dedicated Platform Services Controller site name (Site A, Site B). Each Platform Services Controller node can be used for up to four resource vCenter Server nodes that are installed in the same site and for related resource group management components (VMware NSX Manager™, vSphere Replication Manager).
A third Platform Services Controller node is deployed with Platform Services Controller Site C. This Platform Services Controller node is then used solely by non-resource group components, such as vCloud Director, vSphere Replication Cloud Service servers, and Cassandra., The Platform Services Controller is not site-specific—it can run on any site and fail over to another site (for example with Site Recovery Manager protection).
Figure 11. Platform Service Controller Nodes in Multi-Site Configuration
vCloud Director requires a vSphere Web Client endpoint to exist in the Platform Services Controller Site C LookupService service registration (otherwise the vCloud Director federation with Platform Services Controller node 3 fails). Therefore, an additional VMware vCenter Server Appliance™ must be deployed and registered against Platform Services Controller node 3.
Note All Platform Services Controller nodes must be in the same domain (for example, vsphere.local). It is also possible to deploy each node in a highly available configuration with two nodes in the same site behind a load balancer (as in the single-site case).
