# Active Passive

---

## Active/Passive with failover

- A main, active JFrog Platform deployment ([jfrog-a.my.org]()) used by an organization with a passive JFrog Platform deployment (usually in a different data center) ready for failover ([jfrog-b.my.org]())
- A global DNS CNAME is defined ([jfrog.my.org]()) with routing to ([jfrog-a.my.org]()). In case of a failover is needed, the main DNS will be updated to point to the failover site ([jfrog-b.my.org]())
- All of the organization is using a single URL to access the JFrog Platform ([jfrog.my.org]())
- Using Access and repository federation to keep data and Access entities in sync
- This a common architecture used for DR (Disaster Recovery) readiness where the passive site acts as the backup platform
   - See more details in the [Disaster Recovery](/disaster-recovery/) section
- See [Limitations](../multi-site-limitations)

### Architecture

The following is a schematic high level architecture of such a deployment.

![Active - Passive](../../../../images/active-passive.png)