MajwareMAJWARE
Free templateEditable9 systems9 interfaces

PACS High Availability & Disaster Recovery Diagram

Imaging is a 24/7 clinical service, so the PACS must survive a server failure without anyone noticing, and a site loss with a planned, tested recovery. This diagram shows both layers: an active-active PACS cluster behind a load balancer for high availability inside the data centre, and asynchronous replication to a DR site for disaster recovery.

Open & edit in Diagram Builder →Download SVG

Free, no sign-up. The builder runs in your browser; nothing is uploaded.

PACS High Availability & Disaster Recovery Diagram: Primary data centre, DR site, Modalities, Load Balancer, PACS Node A, PACS Node B, DR PACS, Primary Storage, DR Storage
PACS High Availability & Disaster Recovery Diagram — 9 systems and 9 labelled interfaces. Free to use in your own documentation.

What this diagram shows

Pair it with your RPO and RTO targets and you have the core of a PACS business continuity plan.

Components

Modalities and workstations

Point to one virtual IP and AE title, never to an individual server.

Load balancer

Distributes DICOM associations and web traffic across healthy nodes and takes failed nodes out of service.

PACS nodes A and B

Run the application active-active, sharing the database and storage.

Primary storage

Shared SAN or NAS holding the images, with its own redundancy (RAID, dual controllers).

DR PACS and DR storage

Warm standby at a second site, kept current by database sync and storage replication.

How the data flows

  1. Normal operation

    Modalities send to the virtual AE; the load balancer spreads associations across both nodes.

  2. Node failure

    Health checks fail, the load balancer stops sending to the failed node, and the surviving node carries the load. Senders retry interrupted associations.

  3. Replication

    Storage replicates asynchronously to the DR site and the database ships changes to the DR PACS.

  4. Site failover

    If the primary site is lost, the DR PACS is promoted, DNS or the virtual IP moves, and modalities keep sending to the same AE title.

  5. Failback

    After recovery, changes made at the DR site are synchronised back before service returns to the primary site.

Interfaces in this diagram

Every connection in the diagram, ready to copy into an interface register or test plan.

#FromToProtocolDetail
1Modalities (& Workstations)→Load Balancer (Virtual IP / AE)DICOMVirtual AE
2Load Balancer (Virtual IP / AE)→PACS Node A (Active)DICOM—
3Load Balancer (Virtual IP / AE)→PACS Node B (Active)DICOM—
4PACS Node A (Active)→Primary Storage (SAN / NAS)TCP/IPiSCSI
5PACS Node B (Active)→Primary Storage (SAN / NAS)TCP/IPiSCSI
6PACS Node A (Active)↔PACS Node B (Active)TCP/IPHeartbeat
7Primary Storage (SAN / NAS)→DR Storage (Replica)VPNAsync replication
8PACS Node B (Active)→DR PACS (Warm standby)TCP/IPDB sync
9DR PACS (Warm standby)→DR Storage (Replica)TCP/IP—

Design considerations

  • Agree RPO (how much data you can lose) and RTO (how long you can be down) with clinicians, then design to them.
  • Asynchronous replication means the newest studies may be missing after a site failover — modalities should keep local copies until PACS confirms them with Storage Commitment.
  • Test failover on a schedule and after every upgrade. An untested DR plan is a hope, not a plan.
  • Keep a downtime procedure: modalities store locally and reports go out by an agreed fallback route.
  • Monitor and alert on replication lag, not only on node health.

Related reference

Frequently asked questions

What is the difference between high availability and disaster recovery for PACS?

High availability keeps PACS running through component failures inside one site — a server, disk or network link — usually automatically. Disaster recovery restores service at another site after the primary site is lost, usually through a defined procedure and with possible data loss up to the RPO.

What are typical RPO and RTO targets for PACS?

Each organisation sets them with its clinicians. Diagnostic imaging usually needs an RTO measured in hours rather than days and an RPO close to zero for newly acquired studies, which is why modalities should keep local copies until storage is committed.

Why use a virtual AE title?

If every modality points at one virtual IP and AE title, nodes can fail, be patched or be replaced without reconfiguring dozens of devices.

Make it match your site

Rename systems, add your AE titles and message types, then export PNG, SVG or PDF — or send a colleague a share link.

Open in Diagram Builder →

More architecture templates

All 12 templates →
PACS Architecture Diagram — preview
Imaging

PACS Architecture

Modalities, RIS worklist, PACS image manager, diagnostic and web viewers, and long-term VNA archive.

7 systems · 7 interfaces

Radiology Workflow Diagram (RIS–PACS) — preview
Imaging

Radiology Workflow

End-to-end order-to-report workflow: CPOE order, worklist, acquisition, PACS, reading and reporting.

6 systems · 7 interfaces

DICOM Modality Worklist (MWL) Workflow Diagram — preview
Imaging

Modality Worklist

How an HL7 order becomes a DICOM worklist entry, plus MPPS status and storage to PACS.

5 systems · 5 interfaces