Topic lessonTopic: SQL Server recovery and analytics data
SQL Server disaster recovery trade-offs: RTO, RPO, standby cost and residual risks
Choose a strategy based on measured recovery and what the team can sustain. Use downtime, data-loss and budget requirements to narrow the choices in a fictional comparison.
Use downtime, data-loss and budget requirements to narrow the choices in a fictional comparison.
The measurements and cost scores are fictional. They do not represent service guarantees or actual prices.
Set minimum requirements before comparing strategies
DR strategies include rebuilding from backup, pilot light, warm standby and active deployments at multiple locations. Compare standing infrastructure and steps required during recovery.
- Time and loss goals → Standing cost ceilingSet common measurements
- Standing cost ceiling → Measured resultsFilter by requirements
- Measured results → Residual riskPlan remaining tests
- Time and loss goals
- Within 30 and 5 minutes
- Standing cost ceiling
- At most 10 points
- Measured results
- Verify recovery and data
- Residual risk
- Test corruption and failback
The fastest option can exceed a different constraint
| Strategy | Downtime / data gap | Standing cost score |
|---|---|---|
| Rebuild from backup | 65 min / 12 min | 3 |
| Pilot light | 38 min / 4 min | 6 |
| Warm standby | 22 min / 4 min | 9 |
| Active at multiple sites | 10 min / 2 min | 13 |
Warm standby meets all three requirements in this exercise. Test an earlier recovery point separately because an incorrect update can be replicated.
Record the conditions that remain after choosing
Record test conditions. List fault scope, peak load, recovery connectivity and configuration. Compare measurements instead of strategy names.
Address data corruption. Treat an incorrect update as a separate exercise. Verify the recovery point, isolation and reconciliation.
Assign failback and testing owners. Record return conditions, operating effort, cost scope and measurement date.
Check the worked example
Choose an option to see the result and explanation.
Check, then explain in your own words
- State the objectives and budget.
- Compare measured results under matching conditions.
- Track corruption and failback tests separately.
Check your understanding: Should you always choose the fastest strategy?
Choose against downtime, loss, cost, operational burden and corruption recovery together.
Speed is one of the requirements.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsRecovery from backup, pilot light, standby and multi-site trade-offs.
Used in this lessonSet minimum requirements before comparing strategies The fastest option can exceed a different constraint Record the conditions that remain after choosing