Recovery Time Objective (RTO) and Recovery Point Objective (RPO)
Recovery time objective is the amount of downtime you can tolerate and recovery point objective is the amount of data loss you can tolerate. In the event of a failure, a high availability DB system can achieve a better recovery time objective and recovery point objective as compared to a standalone DB system.
HeatWave Service uses Block Volumes to store user data. In addition to the durability, security, and performance features provided by Block volumes, HeatWave Service has a rich set of features to provide resiliency against different types of failures. The features are automatic and manual backups, point-in-time recovery, cross region backup copy, high availability DB system, inbound and outbound replication, and read replicas.
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 |