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: Audit coverage and recovery design

SQL Server RTO and RPO across a database and external records

Use the latest point where the database and its external records agree. A fictional reporting recovery shows how to assess downtime and data loss separately.

What you will learn

Find a consistent point across SQL Server and related data, then judge downtime and data loss against separate objectives.

Prerequisite

The exercise uses fictional RDS for SQL Server recovery evidence. Familiarity with basic RTO and RPO definitions is assumed.

Define the business outcome after restoring the database

Recovery objectives specify acceptable business downtime and data loss. RDS point-in-time recovery creates another DB instance, so this example includes changing the connection target and checking the business results.

From database restoration to business verification
From database restoration to business verification1: Outage — Record interruption — Restored database. 2: Restored database — Match IDs and contents — Cross-check output. 3: Cross-check output — Record resumption — Business resumes123OutageRestored databaseCross-check outputBusiness resumesFrom database restoration to business verification1: Outage — Record interruption — Restored database. 2: Restored database — Match IDs and contents — Cross-check output. 3: Cross-check output — Record resumption — Business resumes123OutageRestoreddatabaseCross-checkoutputBusinessresumes
  1. Outage → Restored databaseRecord interruption
  2. Restored database → Cross-check outputMatch IDs and contents
  3. Cross-check output → Business resumesRecord resumption
Outage
Reporting stops at 12:00
Restored database
Rows through 11:57
Cross-check output
Reports agree through 11:52
Business resumes
Reports verified at 12:26

Judge the 30-minute and 5-minute objectives

A fictional payment-reporting outage began at 12:00
EvidenceTimeInterpretation
Restored DB accepts connections12:18Reporting has not resumed
Latest confirmed cross-system match11:52Eight-minute data gap
Reporting resumes12:26Twenty-six minutes of downtime
Objective and resultRTO 30 min, RPO 5 minRTO passes; RPO fails

RTO bounds the downtime to business resumption. RPO bounds the acceptable data loss. The last confirmed consistent reporting point is 11:52, although the database contains rows through 11:57.

Record which interval you verified and why operations resumed

Agree on timing conventions. Decide the resolution, time zone and business cutoffs. Separate receipt and creation times from transaction commit time.

Verify connection identity. Confirm that you are looking at the new point-in-time instance, then match business IDs, counts and reporting results to the intended scope.

Record the gap and decision. If resuming outside an objective, document what is missing, whether it can be replayed, how to avoid duplicates and who approved the decision.

Check your decision

Choose an option to see the result and explanation.

How large is the confirmed reporting data gap?
Read the answer and reason

Answer: Eight minutes · The gap from 11:52 to 12:00 is eight minutes.

Which timestamp ends the RTO measurement?
Read the answer and reason

Answer: 12:26 · The goal is resumption of the reporting function.

What is the result against RTO 30 min and RPO 5 min?
Read the answer and reason

Answer: RTO passes; RPO fails · Compare 26 minutes and eight minutes separately.

Check, then explain in your own words

  1. Define when downtime starts and ends.
  2. Match database and external records by a common ID.
  3. Record separate decisions for time and data.
Check your understanding: Can you report a three-minute RPO result because the database restored through 11:57?

For this process use 11:52, the latest point verified in both systems.

The recovery point must be usable for the business process.

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.