While there are countless public documents that talk about the goodness of vRealize Orchestrator, we wanted to pivot our discussion on high availability configuration via the NSX load balancer for vRealize Orchestrator in this chapter. VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) can be configured to work in two server modes: standalone and cluster. To increase the availability of the VMware vRealize Orchestrator services both in standalone and cluster mode, you can put the Orchestrator behind a load balancer.
Starting with vRO 5.5, clustering has been included as an out-of-box option that enables greater availability for the Orchestrator engine. If an active Orchestrator server becomes unavailable midway through a workflow run, another active or the standby Orchestrator node will take over and complete the workflow without any service interruptions. However, we have two known limitations...