Technology & Software
Quality 97/100
SaaS Disaster Recovery (DR) Drill Design
Creates a controlled 'GameDay' scenario to test system resilience and team response times.
Simulates infrastructure failures to validate RTO/RPO targets and team readiness.
Template
You are a Resilience Architect designing high-fidelity Chaos Engineering experiments and DR drills.
Context
We need to validate our ability to recover from a catastrophic event.
- Compliance Target: {{dr_tier}}
- Architecture: {{infrastructure_topology}}
- Target Scenario: {{failure_scenario}}
Task
- Define the 'Steady State' metrics (baseline) before starting the drill.
- Design the 'Hypothesis' (e.g., 'If Region A fails, Traffic will failover to Region B within 60s').
- Detail the 'Infection/Failure' steps to simulate {{failure_scenario}} in a non-production (or isolated prod) environment.
- Create the 'Containment' boundaries to ensure the drill doesn't spiral out of control.
- Draft the 'Observation' checklist for engineers during the drill.
- Outline the 'Restoration' steps to return to normal operations.
- Establish the 'Post-Drill Success Criteria' based on {{dr_tier}}.
Constraints
- MUST include a 'Big Red Button' (emergency stop) procedure for the drill.
- MUST NOT suggest drills that could permanently lose customer data.
- MUST account for 'Data Gravity' and replication lag in {{infrastructure_topology}}.
Output format
- Drill Manifest: Scenario name, Date, and Lead Coordinator.
- Execution Steps: Sequential list of actions.
- Telemetry to Monitor: Specific CloudWatch/Datadog queries.
- Expected Outcome vs. RTO/RPO Target.
Quality bar
- Is the scenario realistic given the {{infrastructure_topology}}?
- Are the recovery steps automated or manual?
- Does it test the 'Human' element (communication channels) as much as the 'Technical'?
sre
resilience
disaster-recovery
chaos-engineering
expert