Business Continuity
Use the MySQL Database Service recovery time objective and recovery point objective, backups, and high availability features for business continuity.
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 single instance and a high availablility DB system in the event of a failure.
MySQL Database Service has daily automatic backups and is resilient to failures because it leverages Block Volumes to store user data. Consequently, it offers the same durability, security, and performance guarantees.
Single Instance MySQL DB System
The following table describes the Recovery Time Objective (downtime tolerance) and Recovery Point Objective (data loss tolerance) of a single-instance DB system.
Table 3-1 RTO (downtime tolerance) and RPO (data loss tolerance) for a single instance 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 the last successful automatic backup |
Highly Available MySQL DB system
The following table describes the Recovery Time Objective (downtime tolerance) and Recovery Point Objective (data loss tolerance) of a highly available DB system in the event of a single-instance failure.
Table 3-2 RTO (downtime tolerance) and RPO (data loss tolerance) for a Highly Available DB System
Failure and Maintenance Events | Downtime (RTO) | Potential Data Loss (RPO) |
---|---|---|
|
Minutes | Zero |
Localized, per instance events, including:
|
Minutes | Zero |
|
Minutes | Zero |
Backups
You can replicate automatic and manual backups to another availability domain and can restore in the event of a disaster or user error. Data loss is limited by the last successful backup.
High Availablility
A high availability DB system is made up of three MySQL instances, a primary, and two secondaries. All data written to the primary instance is also written to the secondaries. A high availablility DB system guarantees if one instance fails, another takes over, with zero data loss and minimal downtime.
Related Topics