DR: Disaster Recovery
The policies, tools, and procedures for recovering technology infrastructure and systems following a natural or man-made disaster.
What is DR?
Disaster recovery focuses specifically on IT system recovery, a subset of broader business continuity planning. Key elements include backup strategies, recovery sites (hot, warm, cold), data replication, failover procedures, and recovery testing. Modern DR increasingly leverages cloud-based recovery solutions. Recovery objectives (RTO and RPO) drive DR architecture decisions. Regular testing is essential to verify that recovery procedures work within required timeframes.
Application to Vendor Screening
For vendors providing technology services, disaster recovery capabilities directly affect your organization's resilience. Due diligence should assess vendor DR architecture, recovery sites, backup procedures, testing frequency, and demonstrated recovery times. Contracts should specify DR requirements aligned with your BIA-derived objectives.
Practical Examples
- Reviewing a vendor's DR architecture including recovery site location and capabilities
- Requiring vendors to conduct annual DR tests and share results
- Verifying that vendor DR capabilities meet your RTO and RPO requirements
Frequently Asked Questions
What are hot, warm, and cold recovery sites?
Hot sites are fully operational duplicates ready for immediate failover. Warm sites have hardware and connectivity but need data restoration. Cold sites have basic infrastructure but require equipment setup and data loading.
How often should vendor DR be tested?
At minimum annually, with more frequent testing for critical services. Tests should verify RTO/RPO achievement and include customer notification. Results should be documented and shared.