Recovery Time Objective (RTO) and Recovery Point Objective (RPO)
View the recovery time objective (downtime tolerance) and recovery point objective (data loss tolerance) details of a standalone and a high availability DB system in the event of a failure.
HeatWave Service has daily automatic backups, point-in-time recovery, and is resilient to failures because it leverages Block Volumes to store user data. Consequently, it offers the same durability, security, and performance guarantees.
Standalone DB System
The following table describes the Recovery Time Objective (downtime tolerance) and Recovery Point Objective (data loss tolerance) of a standalone DB system.
Table 2-1 RTO (downtime tolerance) and RPO (data loss tolerance) for a standalone DB system
| Failure and Maintenance Events | Downtime (RTO) | Potential Data Loss (RPO) |
|---|---|---|
|
Minutes to hours | Zero |
Localized events, including:
|
Minutes to hours | Zero |
Events requiring restoring from backup, including:
|
Minutes to hours | Up to five minutes with point-in-time restore enabled. |
High Availablility DB system
The following table describes the Recovery Time Objective (downtime tolerance) and Recovery Point Objective (data loss tolerance) of a high availablility DB system in the event of a single-instance failure.
Table 2-2 RTO (downtime tolerance) and RPO (data loss tolerance) for a High Availability DB System
| Failure and Maintenance Events | Downtime (RTO) | Potential Data Loss (RPO) |
|---|---|---|
|
Seconds to minutes | Zero |
Localized, per instance events, including:
|
Minutes | Zero |
|
Minutes | Zero |