Recovery Time Objective (RTO) defines the maximum acceptable duration of service interruption following a failure.
For a CyberArk deployment requiring minimal recovery time from individual Vault server failures in both datacenters, high-availability Vault clusters provide an appropriate architecture.
A CyberArk Vault cluster consists of two Vault nodes configured to operate as a single logical Vault service. The Cluster Vault Manager coordinates availability and failover between the active and passive nodes.
If the active node fails, the surviving cluster node can assume operations through the supported failover mechanism, minimizing interruption without requiring a full datacenter disaster recovery procedure.
Deploying a Primary Vault cluster in the primary datacenter and a DR Vault cluster in the secondary datacenter combines local high availability with geographic disaster recovery.
This design protects against individual server failures at either location while retaining a standby recovery environment if the primary datacenter becomes unavailable.
The distinction is important: automatic cluster-node failover does not necessarily mean instantaneous disaster recovery promotion between geographically separated Vault clusters.
Option B directly addresses the customer's requirement for local server-failure resilience at both locations.
[Reference:CyberArk PAM Self-Hosted — Vault Cluster Architecture, Cluster Vault Manager, High Availability, Disaster Recovery and RTO Planning.]
Submit