Topic lessonTopic: Applied GitHub Actions and SQL Server recovery labs
SQL Server recovery exercise|Compare RTO and RPO
RTO is a recovery-time objective. RPO concerns acceptable data loss measured in time. Use consistent timestamps and check both.
Compare the elapsed recovery time and recovered data point independently.
The cases use fictional inputs.
What to predict
RTO is a recovery-time objective. RPO concerns acceptable data loss measured in time. Use consistent timestamps and check both.
- Recovery point age (min) → Elapsed recovery (min)Align conditions
- Elapsed recovery (min) → RPO target (min)Compare outcomes
- RPO target (min) → RTO target (min)Verify the decision
- Recovery point age (min)
- 5 / 15
- Elapsed recovery (min)
- 20 / 45
- RPO target (min)
- 10 / 20
- RTO target (min)
- 30 / 60
Compare the cases
| Case | Conditions | Decision |
|---|---|---|
| Trial 1 | Recovery point age (min) 5, Elapsed recovery (min) 20, RPO target (min) 10, RTO target (min) 30 | Both targets met: data point age 5 min, elapsed recovery 20 min. |
| Trial 2 | Recovery point age (min) 15, Elapsed recovery (min) 20, RPO target (min) 10, RTO target (min) 30 | RPO missed: data point age 15 min, elapsed recovery 20 min. |
| Trial 3 | Recovery point age (min) 5, Elapsed recovery (min) 45, RPO target (min) 10, RTO target (min) 30 | RTO missed: data point age 5 min, elapsed recovery 45 min. |
| Trial 4 | Recovery point age (min) 15, Elapsed recovery (min) 45, RPO target (min) 10, RTO target (min) 30 | Both targets missed: data point age 15 min, elapsed recovery 45 min. |
Acceptance and limits
Uses synthetic minutes. Real SQL Server recovery time and consistency need separate validation.
Read the initial conditions and operational goal.
Change one condition and compare the decision.
Record the model boundary and outstanding checks.
Change a condition
Uses synthetic minutes. Real SQL Server recovery time and consistency need separate validation.
Both targets met: data point age 5 min, elapsed recovery 20 min.
{"met":"Both targets met: data point age {age} min, elapsed recovery {elapsed} min.","data":"RPO missed: data point age {age} min, elapsed recovery {elapsed} min.","time":"RTO missed: data point age {age} min, elapsed recovery {elapsed} min.","both":"Both targets missed: data point age {age} min, elapsed recovery {elapsed} min."}Check your understanding
Choose an option to see the result and explanation.
Check, then explain in your own words
- Read the initial conditions and operational goal.
- Change one condition and compare the decision.
- Record the model boundary and outstanding checks.
Check your understanding: Compare the elapsed recovery time and recovered data point independently.
Uses synthetic minutes. Real SQL Server recovery time and consistency need separate validation.
Record the model boundary and outstanding checks.
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 conditionsRTO is a recovery-time objective. RPO concerns acceptable data loss measured in time. Use consistent timestamps and check both.
Used in this lessonWhat to predict Acceptance and limits