Which service should not be running on the DR Vault when the primary Production Vault is active?

The PrivateArk Server is the core application server for the production vault responsible for executing all server-side logic related to identity and access management. When the primary Production Vault is active, having another instance of the PrivateArk Server running on the DR (Disaster Recovery) Vault would not only duplicate services but could also lead to data conflicts and inconsistencies.

In a disaster recovery scenario, the DR Vault should remain in a standby state, prepared to take over only when the primary vault goes down. By keeping the PrivateArk Server off while the Production Vault is active, vigilance is maintained over the integrity of data and management processes, ensuring that the resources are not being split or compromised between two operational engines.

The other services listed, such as the Replication Service, Backup Service, and Monitoring Service, are typically still beneficial for the DR infrastructure to ensure data continuity, backup, and health status check, even when the Production Vault is operational.