INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Use downtime, data-loss and budget requirements to narrow the choices in a fictional comparison.

Prerequisite

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.

From business objectives to a recovery strategy
From business objectives to a recovery strategy1: Time and loss goals — Set common measurements — Standing cost ceiling. 2: Standing cost ceiling — Filter by requirements — Measured results. 3: Measured results — Plan remaining tests — Residual risk123Time and loss goalsStanding costceilingMeasured resultsResidual riskFrom business objectives to a recovery strategy1: Time and loss goals — Set common measurements — Standing cost ceiling. 2: Standing cost ceiling — Filter by requirements — Measured results. 3: Measured results — Plan remaining tests — Residual risk123Time and lossgoalsStanding costceilingMeasuredresultsResidual risk
  1. Time and loss goals → Standing cost ceilingSet common measurements
  2. Standing cost ceiling → Measured resultsFilter by requirements
  3. 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

Fictional results from the same SQL Server workload under a Region outage.
StrategyDowntime / data gapStanding cost score
Rebuild from backup65 min / 12 min3
Pilot light38 min / 4 min6
Warm standby22 min / 4 min9
Active at multiple sites10 min / 2 min13

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.

Which option meets 30 minutes, 5 minutes and 10 cost points?
Read the answer and reason

Answer: Warm standby · 22 minutes, 4 minutes and 9 points meet all three limits.

An incorrect update is replicated to the standby. Which test is also required?
Read the answer and reason

Answer: Test point-in-time recovery and business reconciliation · Check how to reach a consistent state before the update.

What can you say about the 22-minute outcome?
Read the answer and reason

Answer: This exercise recovered in 22 minutes · It applies to the measured configuration and conditions.

Check, then explain in your own words

  1. State the objectives and budget.
  2. Compare measured results under matching conditions.
  3. 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.