Question

Backups and Point In Time Restore (PITR)

I currently use AWS RDS. Looking at your managed database pages and the documentation it’s not clear if, like AWS, you’re taking snapshots every 5 minutes in addition to the daily backups - or there is only the daily backup?

What is the Recovery Point Objective (RPO) of your managed MySQL databases? This is assuming user error, so a cluster does not help as the mistake will be replicated.


Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

abearfield
DigitalOcean Employee
DigitalOcean Employee badge
January 18, 2020
Accepted Answer

Hey petersys 👋

The service takes a single full backup every 24 hours; the write ahead log (WAL) is backed up approximately every 5 minutes, enabling point-in-time-restore operations.

If user error occurs that needs to be rolled back, the best way to accomplish this is to create a new service from a backup at a point-in-time prior to the error. Once the new service is online, the original service can be destroyed.

abearfield
DigitalOcean Employee
DigitalOcean Employee badge
February 4, 2020

Hey @petersys

Sorry for the delay here. A multi-node setup would have reduced RPO due to standby nodes being promoted and taking over write and read operations right away. For a single-node service, a failure will cause the loss of data in the WAL that has not yet been committed to the backup service (5 min or less as outlined above). For multi-node services, any loss of data is a function replication lag. Replication to standby nodes is asynchronous but close to real-time.

Thanks!

abearfield
DigitalOcean Employee
DigitalOcean Employee badge
January 21, 2020

For a single-node, non-HA services, it is fair to assess the RPO as approximately 5 minutes. Users who require reduced RPO should configure their Managed Database services with one or more standby nodes.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel