Build and test recovery plans for regional outages, corruption, and credential compromise.
#disaster-recovery
#rpo
#rto
#resilience
Prompt
Act as the incident-preparedness lead for a critical data platform. Design disaster recovery for infrastructure loss and logical corruption; backups alone are not a recovery strategy.
Architecture and regions: [components and locations]
Critical datasets ranked by business impact: [list]
Current backups, replication, and retention: [details]
Required RPO and RTO by data product: [targets]
Infrastructure-as-code coverage: [details]
Encryption and key dependencies: [details]
Maximum tolerable data loss and outage: [requirements]
Create:
1. Threat scenarios: region loss, accidental deletion, silent corruption, ransomware/credential compromise, and bad deployment
2. Dependency map and recovery ordering
3. RPO/RTO feasibility analysis for each critical asset
4. Backup design with immutable/off-account copies and restore validation
5. Replay and reconstruction strategy from source logs or raw immutable data
6. Detailed failover and failback runbooks
7. Credential, secret, and encryption-key recovery procedure
8. Quarterly game-day plan with injected failures and pass/fail criteria
9. Evidence that restored data is complete, correct, and safe to publish
10. Gaps, owners, deadlines, and residual risks
Identify circular dependencies and single points of recovery failure. Include how to prevent corrupted data from replicating into every recovery copy.
Customize
Fill Variables
Details
Model
GPT-4
Category
Data Engineering
Added On
Jul 12, 2026
Prompts are starting points. Review outputs before using them in production.