Study guide
12.3 Disaster Recovery, Redundant Connectivity & Evacuation
NENA Emergency Number Professional ENP
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the NENA ENP Exam
2 Chapter 1: 9-1-1 Evolution & Legacy Network Architecture
1.1 Evolution of 9-1-1 & Central Office Tandem Architecture 1.2 Legacy Location Infrastructure: MSAG, ANI, ALI & ESN/ESZ 1.3 Legacy Network Signaling: CAMA, SS7 & Selective Routing 1.4 Network Design: Originating Service Providers, Local Loops & Transport Facilities 1.5 Signaling, Transport Protocols & Transmission Systems 1.6 Types and Features of 9-1-1 Systems: Basic, Enhanced & NG9-1-1
3 Chapter 2: Modern Location Technologies & MLTS
2.1 Wireless 9-1-1: Phase I, Phase II & Location Accuracy 2.2 Device-Based Location, Supplemental Data & RapidSOS 2.3 MLTS Compliance: Kari's Law & RAY BAUM'S Act
4 Chapter 3: NG911 i3 Core Network & Security
3.1 NG911 Architecture: The ESInet & Core Services 3.2 Border Control Function (BCF) & Security Edge 3.3 SIP Signaling in NG911 (RFC 3261) & Emergency Call Flow
5 Chapter 4: NG911 Location Services & Call Routing
4.1 Location Information Server (LIS) & PIDF-LO 4.2 Emergency Call Routing Function (ECRF) & LoST 4.3 Location Validation Function (LVF) & Legacy Gateways 4.4 NG9-1-1 PSAPs, EIDO, Additional Data & Transitional Elements
6 Chapter 5: Public Safety Radio, Broadband & FirstNet
5.1 Land Mobile Radio (LMR) Architecture & P25 Standards 5.2 Conventional vs. Trunked Radio Systems & Frequency Bands 5.3 Public Safety Broadband, FirstNet & Mission-Critical Services
7 Chapter 6: Call Processing, Accessibility & Protocol Systems
6.1 Call Answering Standards & Answering Point Workflows 6.2 Accessibility: TTY/TDD, Text-to-911 & Real-Time Text (RTT) 6.3 Emergency Protocol Systems & Medical Direction 6.4 PSAP Types & 9-1-1 Call Handling Equipment
8 Chapter 7: Computer Aided Dispatch & Information Systems
7.1 Computer Aided Dispatch (CAD) System Architecture 7.2 CAD Interfaces: Mobile Data, RMS & External Telematics 7.3 Logging Recorders & Synchronized Master Clocks 7.4 Non-Voice Communications & Information Networks 7.5 NENA Standards & Other Documents
9 Chapter 8: GIS for Next Generation 9-1-1
8.1 NG911 GIS Data Layers: Road Centerlines & Address Points 8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions 8.3 GIS Data Quality, Topology & Provisioning Workflows 8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management
10 Chapter 9: Cybersecurity & CJIS Compliance
9.1 PSAP Cybersecurity Frameworks: NENA NG-SEC & NIST CSF 9.2 CJIS Security Policy: Access Control, MFA & Encryption 9.3 TDoS, Ransomware & Cyber Incident Response Planning
11 Chapter 10: Telecommunications Policy, Funding & Civil Rights
10.1 Regulatory Governance: FCC Authority & Part 9 Orders 10.2 9-1-1 Surcharges, Fee Diversion & Federal Grant Programs 10.3 Civil Rights & Language Access: Title VI & ADA Title II 10.4 Telecommunications Service Priority, Public Utility Commissions & the Canadian Framework 10.5 Special Legislative Areas: Alarms, Mass Notification, Pipelines & Other 9-1-1 Laws
12 Chapter 11: PSAP Governance, Strategy & Facility Design
11.1 PSAP Governance Models: Standalone, Co-Located & Consolidated 11.2 Strategic Planning & Performance Management 11.3 PSAP Facility Architecture, Physical Security & Ergonomics 11.4 Management Decision Making & Short-Range, Long-Range & Strategic Planning
13 Chapter 12: Power Redundancy, COOP & Disaster Recovery
12.1 Electrical Power Redundancy: UPS Systems & Generator Sets 12.2 Continuity of Operations Planning (COOP) & Alternate Facilities 12.3 Disaster Recovery, Redundant Connectivity & Evacuation 12.4 Emergency Management: Disaster Types & the Four Phases
14 Chapter 13: Emergency Incident Management & NIMS/ICS
13.1 National Incident Management System (NIMS) & ICS Architecture 13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces 13.3 Mutual Aid & Interagency Interoperability: MACS & MABAS
15 Chapter 14: Procurement, Contracts & Financial Management
14.1 Capital Budgeting, Operational Expense & Financial Auditing 14.2 Public Procurement: RFPs, RFQs & Bid Evaluations 14.3 Vendor Contracting: MSAs, SLAs & Life-Cycle Management
16 Chapter 15: Staffing Models, Scheduling & Wellness
15.1 PSAP Staffing Models: Erlang C & NENA Staffing Calculator 15.2 Shift Scheduling Models, Overtime & Fatigue Mitigation 15.3 Telecommunicator Wellness: CISM, Peer Support & PTSD
17 Chapter 16: Training, CTO Coaching & Quality Assurance
16.1 Adult Learning & Communications Training Officer (CTO) Models 16.2 Quality Assurance & Continuous Quality Improvement (APCO/NENA ANS 1.107) 16.3 Continuing Education, Certifications & Professional Pathways 16.4 Performance Management, Employee Feedback & Customer Service
18 Chapter 17: Employee Relations, Labor Standards & Legal Protections
17.1 Fair Labor Standards Act (FLSA) & Dispatcher Overtime Rules 17.2 EEO, Title VII, FMLA & ADA in the PSAP Workplace 17.3 Progressive Discipline, Just Cause & Union Negotiations 17.4 Employee Relations, Employment Rights & Labor-Management Relations 17.5 Employment Laws: ADEA, Pregnancy Protections, Uniform Guidelines, OSH Act & Canadian Law 17.6 Compensation Laws: Equal Pay Act, COBRA, Social Security Act & Affordable Care Act
19 Chapter 18: Records Governance, Liability & Public Relations
18.1 Public Records, FOIA & Recording Retention Schedules 18.2 Legal Liability, Tort Claims Acts & Immunity Doctrines 18.3 Public Relations, Media Inquiries & Community Outreach
20 Chapter 19: Recruiting, Hiring, Compensation & Retention
19.1 Recruiting: Workforce Needs, Outreach & Sourcing 19.2 Hiring Procedures: Testing, Interview Panels, Agency Tours & Background Checks 19.3 Compensation & Benefits: Job Analysis, Pay Structures & Medical Benefits 19.4 Employee Retention & Succession Planning
12.3 Disaster Recovery, Redundant Connectivity & Evacuation
Key Takeaways Explain This Topic AI
A critical distinction separates COOP from Disaster Recovery (DR): COOP focuses on people, leadership succession, and continuing operational mission functions (PMEFs), whereas DR focuses on restoring IT systems, database transactions, and network communications infrastructure.
Recovery Time Objective (RTO) defines maximum tolerable downtime while Recovery Point Objective (RPO) defines maximum acceptable data loss, dictating synchronous replication (RPO = 0, < 50–100 km) for local CAD clustering and asynchronous replication for wide-area disaster recovery.
The 3-2-1 backup strategy protects against modern public safety ransomware by maintaining 3 total copies of critical data on 2 different media formats, with at least 1 immutable, air-gapped or WORM copy off-site.
Physical network diversity requires eliminating all common points of failure: dual trenching paths with diverse physical conduits, entrance vaults on opposite building walls, distinct telecommunications carriers, and BGP multihoming.
During an emergency PSAP evacuation, immediate life safety of personnel is the absolute first priority; automated call diversion macros must be initiated rapidly, followed by deployment of tactical Go-Kits and Tactical Dispatch Teams (TDTs).
Last updated: September 2026
12.3 Disaster Recovery, Redundant Connectivity & Evacuation
Quick Answer: Disaster Recovery (DR) and Continuity of Operations (COOP) are complementary public safety disciplines: COOP addresses people, processes, leadership succession, and operational mission survival (PMEFs), while DR focuses on technical restoration of IT systems, databases, network connectivity, and hardware. Key recovery metrics include Recovery Time Objective (RTO) (maximum allowable downtime) and Recovery Point Objective (RPO) (maximum acceptable data loss in time). Mission-critical CAD architectures deploy synchronous database replication locally (RPO = 0) and asynchronous replication across geographically separated wide-area links. Public safety data is secured against ransomware via the 3-2-1 immutable backup rule . Telecommunications ingress must enforce true physical diversity (diverse conduits, separate building vaults, distinct carrier backbones, and BGP-4 multihoming). During sudden facility emergencies, immediate life safety is the absolute first priority, supported by automated 9-1-1 call diversion, tactical Go-Kits, and mobile Tactical Dispatch Teams (TDTs).
1. Disaster Recovery (DR) vs. Continuity of Operations (COOP)
Emergency Number Professionals must understand the operational boundary and functional intersection between COOP and Disaster Recovery: ┌────────────────────────────────────────┬────────────────────────────────────────┐
- │ CONTINUITY OF OPERATIONS (COOP) │ DISASTER RECOVERY (DR) │
- ├────────────────────────────────────────┼────────────────────────────────────────┤
- │ • People, leadership, and operational │ • Technology, servers, databases, and │
- │ workflow focused. │ telecommunications networks focused. │
- │ • Preserves Primary Mission Essential │ • Restores technical computing platforms│
- │ Functions (PMEFs). │ and data repositories to service. │
- │ • Manages evacuation logistics, staff │ • Manages database rebuilds, server │
- │ transit, and alternate site seating. │ failover, SAN replication, and WANs. │
- │ • Driven by operational supervisors, │ • Driven by systems engineers, network │
- │ ECC directors, and public safety SOPs│ architects, and hardware vendors. │
- └────────────────────────────────────────┴────────────────────────────────────────┘
While COOP dictates where telecommunicators will sit and how they will dispatch calls , Disaster Recovery provides the replicated CAD data, restored telephony paths, and synchronized radio networks that allow those telecommunicators to function.
2. Mission-Critical Recovery Metrics: RTO, RPO & MTTR
In public safety system architecture, vague recovery goals such as "restore as fast as possible" are unacceptable. System resilience is governed by mathematically bounded metrics established through a formal Business Impact Analysis (BIA) : [Last Data Commit / Backup] [Disaster Occurs] [System Restored]
- │ │ │
- ├───────────────────────────────────┼────────────────────────────┤
- │◄──────── RPO Window ─────────────►│◄─────── RTO Window ───────►│
- │ (Max acceptable data loss in time)│ (Max acceptable downtime) │
Recovery Time Objective (RTO): The maximum tolerable length of time that a system, network, or application can remain offline following a catastrophic event before severe operational failure occurs. RTO looks forward in time from the moment of disruption to the moment of restoration.
Recovery Point Objective (RPO): The maximum acceptable age of transactional data that can be permanently lost when a catastrophic event strikes, measured backward in time from the failure to the most recent uncorrupted data commit. RPO determines the required replication frequency and database architecture.
Mean Time Between Failures (MTBF): The statistical predicted elapsed operational time between inherent system failures during normal operations.
Mean Time to Repair (MTTR): The average time required to troubleshoot, replace, and restore a failed hardware or software component to service.
Public Safety System Benchmarks
Public Safety System Target RTO (Downtime) Target RPO (Data Loss) Architectural Strategy
9-1-1 Call Routing / NG911 Core < 30 seconds 0 seconds (Zero loss) Active-Active ESInet / ESRP geo-diverse routing
Computer-Aided Dispatch (CAD) < 5 to 15 minutes < 10 seconds / Near-Zero Synchronous local clustering; async off-site replica
- Radio Dispatch Consoles < 10 seconds 0 seconds Dual site controllers; diverse T1/Ethernet loops
- Digital Logging Audio Recorders < 1 hour < 1 minute Continuous real-time streaming to off-site mirrored SAN
- GIS Geodatabases (NG911) < 2 to 4 hours < 24 hours Daily differential snapshots; weekly full baseline
- Administrative RMS / Records < 24 hours < 12 to 24 hours Nightly backup to immutable cloud storage
- 3. Database Resiliency: Synchronous vs. Asynchronous Replication
To prevent losing active incident cards, unit statuses, and call logs during a server room catastrophe, CAD databases cannot rely solely on periodic backups. They require real-time database replication. SYNCHRONOUS REPLICATION (Zero Data Loss - Distance Limited)
- [CAD App] ──► [Primary DB] ──► (Network Write) ──► [Secondary DB]
- ▲ │
- │◄────────── (Write Confirmed) ────────┘
- [Transaction Confirmed to CAD]
* Guarantees RPO = 0. Round-trip network latency limits distance (< 50–100 km).
- ASYNCHRONOUS REPLICATION (Zero Latency Penalty - Unlimited Distance)
- [CAD App] ──► [Primary DB] ──► [Transaction Confirmed to CAD Immediately]
- │
- └──► (Pushed across WAN in background) ──► [Remote DR DB]
* Eliminates application lag; allows 500+ mile separation; minimal RPO risk (seconds).
Synchronous Replication
In synchronous database replication, when the CAD application writes a record (e.g., dispatching an EMS unit), the primary database writes the transaction locally and simultaneously transmits it to a secondary database node. The primary database does not commit the transaction or confirm completion to the CAD application until the secondary node acknowledges that the data has been successfully written .
Advantage: Guarantees absolute zero data loss ( RPO = 0 ). If the primary server suddenly loses power, the secondary replica is identical.
Constraint: The speed of light in fiber optic cables (~5 microseconds per kilometer) and network switching introduce round-trip latency. If the secondary data center is 300 miles away, every synchronous write waits for a round trip (several milliseconds of fiber delay plus network and database processing), which can make CAD noticeably sluggish. For that reason, synchronous replication is usually kept to local or metro data centers (commonly within about 100 kilometers ).
Asynchronous Replication
In asynchronous replication, the primary database commits the transaction locally and confirms completion to the CAD application immediately. In the background (milliseconds later), the transaction log is batched and transmitted across the Wide Area Network (WAN) to the remote disaster recovery database.
Advantage: Zero application latency penalty. CAD operates at full speed, and the remote database can be located hundreds of miles away in another state, completely outside the regional disaster footprint.
Constraint: Introduces a fractional-second "replication lag." If a catastrophe destroys the primary site before data in flight reaches the remote node, transactions in that micro-window are lost, yielding an RPO of seconds .
The Hybrid Public Safety Architecture
Leading public safety centers implement a three-node hybrid model : A primary CAD server in Data Center 1 synchronously replicates to an active-passive node in Data Center 2 (located 25 miles away, delivering RPO=0 high availability), while asynchronously replicating to Data Center 3 located 400 miles away in an independent power grid (providing catastrophic disaster recovery).
4. Immutable Backups & The 3-2-1 Rule
Ransomware represents one of the greatest operational threats to public safety IT infrastructure. Modern threat actors deliberately compromise administrative domain credentials, locate backup servers, and delete or encrypt all backup volumes before encrypting production databases. THE 3-2-1 IMMUTABLE BACKUP RULE
- ┌─────────────────────────────────────────────────────────────┐
- │ 3 Total Copies of Critical Data │
- │ (1 Primary Production Volume + 2 Dedicated Backups) │
- ├─────────────────────────────────────────────────────────────┤
- │ 2 Different Storage Media Formats │
- │ (e.g., High-Speed Local NVMe/SAN Array + Cloud Object Store)│
- ├─────────────────────────────────────────────────────────────┤
- │ 1 Copy Stored Off-Site in an Immutable / WORM Repository │
- │ (Write-Once-Read-Many; Cryptographically Locked Against │
- │ Deletion or Modification Even by Domain Administrators) │
- └─────────────────────────────────────────────────────────────┘
- Write-Once-Read-Many (WORM) & Object Locking
To ensure survivability against ransomware, off-site backups must enforce Immutability (WORM storage) :
Once written, backup objects cannot be overwritten, encrypted, renamed, or deleted by any user, process, API call, or compromised domain administrator account until a predetermined legal retention timer (e.g., 30 or 90 days) expires.
Cloud object storage repositories (such as AWS S3 Glacier Object Lock in Compliance Mode or Azure Immutable Blob Storage) enforce kernel-level cryptographic immutability that cannot be overridden even by cloud account administrators.
5. Redundant Telecommunications Ingress & Physical Path Diversity
A resilient public safety communications center cannot rely on a single fiber connection, regardless of promised carrier reliability. True network path diversity requires eliminating every single physical point of failure between the serving central offices and the dispatch floor. [Public Safety ECC Facility]
- │ │
- ┌─────────────────────────┘ └─────────────────────────┐
- ▼ ▼
- [Entrance Vault A (North Wall)] [Entrance Vault B (South Wall)]
- │ (Conduit Path 1 - North Street) │ (Conduit Path 2 - South Ave)
- ▼ ▼
- [Carrier A - Fiber Optic Ring] [Carrier B - Fiber Optic Ring]
- │ │
- ▼ ▼
- [Central Office 1 (Downtown)] [Central Office 2 (Uptown)]
Four Layers of Network Diversity:
Diverse Physical Conduits: External fiber cables must travel through completely separate underground trenching routes and duct banks along separate municipal street rights-of-way. Minimum physical separation (typically at least 50 to 100 feet) ensures that a single construction excavator cannot sever both paths.
Diverse Building Entrances: Feeder conduits must penetrate the building through two separate entrance vaults (Points of Presence - POPs) located on opposite exterior walls of the structure (e.g., North entrance and South entrance).
Carrier & Central Office Diversity: Circuits must be contracted through two completely independent Tier 1 telecommunications service providers utilizing separate fiber sheaths and routing to two distinct carrier Central Office wire centers.
Internal Cable Risers: Inside the facility, cables from Entrance Vault A and Entrance Vault B must route through separate, fire-rated risers and conduit runs to redundant telecommunications equipment rooms.
BGP Multihoming & Autonomous System Routing
At the network routing layer, redundant internet and ESInet connections must deploy Border Gateway Protocol version 4 (BGP-4) Multihoming :
The 9-1-1 authority obtains its own public Autonomous System Number (ASN) and Provider-Independent (PI) IP address space from the regional internet registry (ARIN).
Edge routers establish BGP peering sessions with both independent service providers simultaneously.
If Carrier A suffers a fiber break or core routing failure, BGP routing tables automatically withdraw Carrier A's routes and redirect all incoming and outgoing IP traffic across Carrier B in seconds, with zero renumbering of internal CAD servers, IP phones, or dispatch consoles .
6. PSAP Evacuation Protocols & Tactical Execution
When a catastrophic facility event (such as a structural breach, chemical spill, or fire) requires abandoning the dispatch floor, the evacuation must execute under structured, pre-planned standard operating procedures.
Life Safety as the Paramount Priority
In any sudden, life-threatening emergency, the immediate life safety of communications personnel is the first and absolute priority . Telecommunicators must never delay evacuation to dismount server hardware, pack paper files, or attempt manual data backups. Facilities and electronics are replaceable; human lives are not.
Tactical Evacuation Sequence:
Fast Emergency Transfer Initiation (Immediate - < 30 Seconds): Before stepping away from the consoles, the shift supervisor activates the automated 9-1-1 call diversion macro. In NG911 environments, this triggers an administrative PRF policy routing rule at the ESRP, redirecting all incoming calls to the backup center or mutual aid partner. In legacy environments, the supervisor hits a speed-dial macro or alerts the carrier NOC.
Immediate Field Responder Notification: Broadcast a standardized emergency evacuation announcement over all primary dispatch talkgroups (e.g., "All units, Communications is evacuating the primary facility due to an emergency. Mutual aid partner County Central is assuming primary dispatch authority until further notice." ).
Deployment of the Tactical Go-Kit: The designated supervisor grabs the hardened Go-Kit, which contains pre-configured portable radios, extra batteries, cellular hotspots, MFA hardware tokens, administrative credential rosters, and facility master fobs.
Evacuation & Personnel Accountability: Staff exit via designated emergency routes to the primary assembly point. A formal Personnel Accountability Report (PAR) is completed immediately.
Deployment of Tactical Dispatch Teams (TDT): A dedicated, pre-designated cadre of tactical dispatchers transits directly to the alternate backup facility or on-scene Tactical Command Post equipped with portable radio caches to re-establish primary dispatch operations.
7. Post-Incident Debriefing: Hotwash, AAR & Improvement Plans
The disaster recovery lifecycle concludes with translating operational challenges into institutional policy improvements following the Homeland Security Exercise and Evaluation Program (HSEEP) model: [Disaster Recovery / Evacuation Event Concludes]
- │
- ▼
- ┌─────────────────────────────────────────────────────────────┐
- │ 1. Operational Hotwash (Immediate - within 2 to 4 hours) │
- │ - Informal, raw capture of operational friction points │
- ├─────────────────────────────────────────────────────────────┤
- │ 2. Multi-Agency Debriefing (Within 5 to 7 business days) │
- │ - Structured timeline analysis across all stakeholders │
- ├─────────────────────────────────────────────────────────────┤
- │ 3. After Action Report (AAR) (Formal written document) │
- │ - Detailed chronological analysis of operational actions │
- ├─────────────────────────────────────────────────────────────┤
- │ 4. Improvement Plan (IP) (Actionable accountability matrix) │
- │ - Specific corrective tasks, assigned owners, and │
- │ measurable completion deadlines │
- └─────────────────────────────────────────────────────────────┘
- The Improvement Plan (IP) Matrix
An After Action Report without an actionable Improvement Plan (IP) is useless. The IP must convert findings into measurable accountability tasks:
Identified Operational Gap Core Capability Corrective Action Required Assigned Owner Target Deadline
Backup site CAD workstations experienced 45-second login delays due to expired SSL certs. Information Technology / CAD Implement automated enterprise PKI certificate lifecycle renewal across all DR cluster nodes. Senior Systems Engineer 30 Days
Telecommunicators lacked physical access keys to backup facility exterior doors. Facilities / Physical Security Re-key backup facility to primary master fobs; add fobs to tactical Go-Kits. Facilities Operations Mgr 14 Days
Radio console talkgroups for rural fire district failed to patch to backup tower. Operational Communications Reconfigure base station control lines and update console alias profiles. Radio Systems Director 60 Days
8. Operational Traps & ENP Exam Watch
COOP vs. Disaster Recovery: COOP is operational and organizational (people, leadership, mission functions, alternate sites). DR is technical and data-centric (restoring servers, databases, and network connectivity).
Synchronous Replication Over Long Distances: A common engineering mistake is attempting synchronous database replication across facilities separated by hundreds of miles. Round-trip network latency will freeze active CAD consoles. Long-distance replication must always be asynchronous.
True Network Diversity vs. Shared Conduits: Two fiber contracts from different vendors do not provide diversity if both carriers share the same underground conduit, bridge crossing, or utility trench. True diversity requires separate physical pathways from the street to the server room.
Life Safety Supersedes Equipment: In any sudden emergency evacuation scenario, never choose an answer option that involves delaying evacuation to dismount servers, back up files, or salvage equipment.