Standby orchestrator

The standby orchestrator is introduced to automatically detect the failure by establishing connectivity between two orchestrators. The existing instance is the active orchestrator and the new instance is the standby orchestrator.

The active orchestrator runs 3-site data cycling and track status of the standby orchestrator. The standby orchestrator acts as a backup during the detection of existing instance failure. After certain time, it assumes the role of active orchestrator and takes over 3-site data cycling. You can configure and manage the standby orchestrator by using the command-line interface (CLI).

Orchestrator communication

The following figure shows how active and standby orchestrators communicate through the auxiliary-far site. The active orchestrator analyzes both orchestrators to identify their states and determine which has the active role. To detect failures, the partner orchestrators actively monitor each other's health.

If an active orchestrator fails and not able to recover, the standby orchestrator based on analysis of state takes over the role of active orchestrator.