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: 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.

What you will learn

Compare the elapsed recovery time and recovered data point independently.

Prerequisite

The cases use fictional inputs.

Start the exercise →

What to predict

RTO is a recovery-time objective. RPO concerns acceptable data loss measured in time. Use consistent timestamps and check both.

From conditions to the decision
From conditions to the decision1: Recovery point age (min) — Align conditions — Elapsed recovery (min). 2: Elapsed recovery (min) — Compare outcomes — RPO target (min). 3: RPO target (min) — Verify the decision — RTO target (min)123Recovery point age(min)Elapsed recovery (min)RPO target (min)RTO target (min)From conditions to the decision1: Recovery point age (min) — Align conditions — Elapsed recovery (min). 2: Elapsed recovery (min) — Compare outcomes — RPO target (min). 3: RPO target (min) — Verify the decision — RTO target (min)123Recovery pointage (min)Elapsedrecovery (min)RPO target (min)RTO target (min)
  1. Recovery point age (min) → Elapsed recovery (min)Align conditions
  2. Elapsed recovery (min) → RPO target (min)Compare outcomes
  3. 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

Synthetic observations
CaseConditionsDecision
Trial 1Recovery point age (min) 5, Elapsed recovery (min) 20, RPO target (min) 10, RTO target (min) 30Both targets met: data point age 5 min, elapsed recovery 20 min.
Trial 2Recovery point age (min) 15, Elapsed recovery (min) 20, RPO target (min) 10, RTO target (min) 30RPO missed: data point age 15 min, elapsed recovery 20 min.
Trial 3Recovery point age (min) 5, Elapsed recovery (min) 45, RPO target (min) 10, RTO target (min) 30RTO missed: data point age 5 min, elapsed recovery 45 min.
Trial 4Recovery point age (min) 15, Elapsed recovery (min) 45, RPO target (min) 10, RTO target (min) 30Both 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.

Check your understanding

Choose an option to see the result and explanation.

What happens in trial 1?
Read the answer and reason

Answer: Both targets met: data point age 5 min, elapsed recovery 20 min. · 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.

What happens in trial 2?
Read the answer and reason

Answer: RPO missed: data point age 15 min, elapsed recovery 20 min. · 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.

What happens in trial 3?
Read the answer and reason

Answer: RTO missed: data point age 5 min, elapsed recovery 45 min. · 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.

Check, then explain in your own words

  1. Read the initial conditions and operational goal.
  2. Change one condition and compare the decision.
  3. 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.