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.
Find a consistent point across SQL Server and related data, then judge downtime and data loss against separate objectives.
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.
- Outage → Restored databaseRecord interruption
- Restored database → Cross-check outputMatch IDs and contents
- 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
| Evidence | Time | Interpretation |
|---|---|---|
| Restored DB accepts connections | 12:18 | Reporting has not resumed |
| Latest confirmed cross-system match | 11:52 | Eight-minute data gap |
| Reporting resumes | 12:26 | Twenty-six minutes of downtime |
| Objective and result | RTO 30 min, RPO 5 min | RTO 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.
Check, then explain in your own words
- Define when downtime starts and ends.
- Match database and external records by a common ID.
- 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.
Scope and conditionsSet downtime and data-loss objectives from business impact and dependencies.
Used in this lessonDefine the business outcome after restoring the database Judge the 30-minute and 5-minute objectives
Scope and conditionsRDS point-in-time restore and its target DB instance.
Used in this lessonDefine the business outcome after restoring the database Record which interval you verified and why operations resumed