Help Center/ Well-Architected Framework/ Well-Architected Framework and Practices/ Resilience Pillar/ Concepts/ Availability Objectives/ RTO and RPO

Updated on 2025-05-22 GMT+08:00

View PDF

RTO and RPO

Recovery Time Objective (RTO) and Recovery Point Objective (RPO) are two critical metrics used to define the recovery objectives in a disaster recovery plan.

RTO is the maximum acceptable length of time that your application can be offline. Your RTO determines what DR method you will need for your application: cold backup, warm backup, or hot backup.
RPO is the maximum acceptable length of time during which data might be lost from your application due to a major incident. RPO determines the backup frequency and method (whether online or offline, synchronous or asynchronous).

Parent topic: Availability Objectives

Previous topic: Availability and SLO

Next topic: Data Durability

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.