# Set and test RTO and RPO

Taiga Learning · Worksheet
https://taiga.training/en/lessons/disaster-recovery/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Distinguish RTO from RPO and availability.
- Calculate elapsed recovery time and the data recovery gap.
- Specify a recovery exercise with evidence and a service owner.

## Exercise
A fictional service stops at 10:00. Detection takes 8 minutes, a decision takes 12, restoration takes 25, and validation takes 10. The latest usable data is from 09:40. Compare the result with RTO 60 minutes and RPO 15 minutes. Propose one improvement for each objective.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
RTO and RPO are business objectives. A measured recovery exercise shows whether the complete service can meet them for a defined scenario.

## Sources
- [AWS: Define recovery objectives for downtime and data loss](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/rel_planning_for_recovery_objective_defined_recovery.html)
- [AWS: Use defined recovery strategies](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/rel_planning_for_recovery_disaster_recovery.html)
- [AWS: Testing disaster recovery](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/testing-disaster-recovery.html)

This worksheet supports learning. Completing it does not itself authorize a production change.