← Archyscape

Disaster recovery (DR) pair diagram

A primary site and a DR site side by side, with storage replication, database log shipping and the GSLB failover on one canvas.

Open this example in the editor →

L2 · ServicesUserssame addressGSLB · DNShealth checksBusiness appactiveBusiness DBactiveBusiness appstandbyBusiness DBstandbyL1 · EquipmentFirewallprimaryCore switchprimaryApp serverprimaryDB serverprimaryStorage (sour…100TBFirewallDRCore switchDRApp serverDR · standbyDB serverDR · standbyStorage (repl…100TBL0 · SitesPrimary site (Seoul)DR site (Daejeon)
Layer by layer

The site layer holds the primary site in Seoul and the DR site in Daejeon; the equipment layer mirrors firewalls, core switches, app and DB servers and storage on both sides. The leased line and the async storage replication (RPO 15 minutes) are written on the connections themselves, so the recovery point objective is readable straight off the picture.

The "Primary fails → switch to DR" scenario steps from normal replication to GSLB failing over and the standby database being promoted. It is a handy way to explain, in a drill plan or an audit, what moves where and in which order when the primary goes down.

What's on each layer

Flow scenario

Primary fails → switch to DR

  1. Storage (source) → Storage (replica) — Normally: storage replicates every 15 min
  2. Business DB → Business DB — DB logs shipped
  3. GSLB · DNS → Business app — Primary stops answering → switch to DR
  4. Business app → Business DB — DR app starts · standby DB promoted
  5. Users → GSLB · DNS — Users reconnect to the same address

Good for

Open this example in the editor →

More examples