Topic lessonTopic: Backup and recovery foundations
RTO vs RPO explained: recovery timelines and backup basics
RTO limits how long a service can be down; RPO limits how much recent change can be lost, expressed as time. Read the two intervals on one timeline using a fictional report service, then distinguish recovery evidence from the mere existence of a backup.
Distinguish interruption, recovered data point and service restoration; assess RTO and RPO separately and identify missing evidence rather than assuming success.
Know that a backup supplies material used for recovery. No AWS or SQL Server configuration experience is required. This lesson uses fictional times without live restore operations or input of real data or credentials.
RTO limits downtime; RPO limits tolerable data loss
RTO (Recovery Time Objective) sets the acceptable duration from service interruption to restored service. RPO (Recovery Point Objective) sets the acceptable data loss expressed as a time gap before the interruption. These are requirements set in advance, not the measured duration of a restore job or its backup schedule.
| Objective | What does it limit? | Result compared in this lesson |
|---|---|---|
| RTO: 30 minutes | Maximum acceptable service interruption | Elapsed time from interruption until the agreed service restoration condition passes |
| RPO: 5 minutes | Maximum tolerable data loss before interruption, measured as time | Gap between interruption and the point represented by the recovered data |
Read two intervals on the same timeline
A fictional report service fails at 10:00. We stipulate that validated recovered data contains committed changes through 09:50 and users can read the required report at 10:25. All times use the same day and Japan Standard Time (JST). These are supplied teaching facts, not AWS measurements; no new writes occur after the interruption.
Same day, JST. Cards show time order; their spacing is not a time scale. These are not AWS measurements.
- Recovered data point
Committed changes through this point are stipulated to be included.
- Service interruption
The internal report becomes unavailable to its users.
- Report check passes; service restored
Required data and user report access are stipulated to pass.
Data-point gap: 10 minutes
10:00 − 09:50 = 10 min
Exceeds the 5-minute target. The required data point is 09:55 or later.
Outage duration: 25 minutes
10:25 − 10:00 = 25 min
Within the 30-minute target. Service restoration is due by 10:30.
Both bars use a 0–30 minute scale. Fill shows the supplied interval; the dashed line marks its target.
The ten-minute gap describes the time range of changes potentially absent from the restored data. It does not mean a known number of records was lost, or that every record from those minutes is irretrievable. Identify missing changes and any possible reconciliation separately.
| Time | Supplied event |
|---|---|
| 10:00 | Service interruption: start counting the outage |
| 10:05 | Restore job starts |
| 10:20 | Job ends; the report check is not yet complete |
| 10:25 | Required data, destination and report checks pass; service is restored |
Backup interval, retention and PITR answer different questions
| Condition | Question it answers | What it does not establish |
|---|---|---|
| Backup interval | How often are captures scheduled or performed? | Successful capture, the data point available, or successful recovery |
| Retention period | How far back is restore material retained? | The latest usable point or all material required for a chosen time |
| Point-in-time recovery (PITR) | Which point within the supported window should be restored? | Recovery outside the window, a guaranteed duration or business consistency |
If all you know is a five-minute schedule, achievement of a five-minute RPO is unconfirmed. Check capture success, the data point covered, required material such as logs, and usable restored results. A job completion timestamp is not automatically the point represented by its data.
For Amazon RDS DB-instance PITR, inspect the actual earliest and latest restorable times. Configured retention does not establish recovery through the present instant. PITR creates a new DB instance rather than overwriting the source, so plan application cutover separately. This scope does not cover every Aurora or backup product.
Choose a usable recovery point, not merely the newest one
With the same 10:00 outage, an erroneous update at 09:54 may remain in a 09:59 recovery point. Selecting a validated clean point at 09:53 gives a seven-minute gap. Choosing correct data and meeting a five-minute RPO are separate judgments. Report the missed target and review missing changes and next actions.
- Record the workload, incident, RTO/RPO targets and service restoration condition; use a consistent time basis.
- Match required data, configuration and dependencies to the restore material, point and destination.
- Restore in an appropriate isolated environment and validate required data and consistency.
- Check the intended application destination, permissions and required reads or writes.
- Record cutover and completion of the restoration condition, then compare outage duration and data-point gap separately with their targets.
Existing lessons below cover SQL Server recovery models, log continuity and RDS for SQL Server restore methods. RDS SQL Server also has a cross-database transaction consistency boundary. Choosing a timestamp is not evidence that the complete business state is consistent.
Check your decisions using times and evidence
Choose an option to see the result and explanation.
Check, then explain in your own words
- Separate targets from observed results.
- Calculate outage duration and data-point gap on one timeline.
- Identify backup, PITR and post-restore validation evidence.
Check your understanding: Does a five-minute backup schedule show that the 30-minute RTO and 5-minute RPO targets have been met?
No. Establish the usable data point and time until restored service separately.
A schedule is not evidence that targets were met. Required material, recovered data and the service restoration condition need validation.
Sources and conditions checked
Primary references are collected here with their scope, conditions and corresponding sections. Independent expert review and live-environment validation have not been performed.
Scope and conditionsRecovery objectives (RTO and RPO); business impact and cost. Definitions only; no measured capability.
Used in this lessonRTO limits downtime; RPO limits tolerable data loss Read two intervals on the same timeline Check your decisions using times and evidence
Scope and conditionsWorkload-specific targets, dependencies and business/technical decisions. No universal numeric target.
Used in this lessonRTO limits downtime; RPO limits tolerable data loss Choose a usable recovery point, not merely the newest one
Scope and conditionsValidate restored data and recovery duration; backup existence or successful restore task alone is insufficient.
Used in this lessonRead two intervals on the same timeline Backup interval, retention and PITR answer different questions Choose a usable recovery point, not merely the newest one Check your decisions using times and evidence
Scope and conditionsRDS DB-instance PITR: earliest/latest restorable time, new instance, background initialization, SQL Server cross-database consistency boundary. Not Aurora or all backup products.
Used in this lessonBackup interval, retention and PITR answer different questions Choose a usable recovery point, not merely the newest one Check your decisions using times and evidence
Scope and conditionsRetention is distinct from a recovery-point objective. No numeric default or configuration instructions are taught here.
Used in this lessonBackup interval, retention and PITR answer different questions