Design & price my architecture →What is it?
BC keeps the service running during a disaster (redundancy, failover, multiple sites); DR restarts the business afterwards (backups, recovery site). Two indicators drive sizing: RPO (max tolerable data loss) and RTO (max recovery time).
Business benefits
- Resilience: an incident at one site does not stop your business.
- Synchronous replication (< 100 km, near-zero RPO) or long-distance asynchronous as needed.
- Geographic AND carrier diversity on each link to remove any single point of failure.
- Demonstrable compliance (ISO 22301, sector requirements).
Enterprise use cases
- An IT team replicates production to a second data center under 2 ms for near-zero RPO.
- A healthcare provider secures HDS data on a sovereign backup site.
- A manufacturer protects its ERP against production stoppage.
FAQ
What distance between primary and backup site?
A short distance (< 100 km) enables synchronous replication (near-zero RPO); a greater distance protects against regional disasters but requires asynchronous. It's a trade-off based on your RPO/RTO.
How do I ensure my IP addresses survive a failover?
By having the same IP prefix announced independently at both sites by a carrier present on both — co-presence is verifiable, and DataColoc shows it.
Are DR and BC the same?
No: BC keeps the service running during the disaster; DR restarts it after. Both are designed together.
Design & price my architecture → Compare data centers
Related solutions
Expert answers → · Solutions