Should I stick only to AWS RDS Automated Backup or DB Snapshots?

MysqlAmazon Web-ServicesAmazon Rds

Mysql Problem Overview


I am using AWS RDS for MySQL. When it comes to backup, I understand that Amazon provides two types of backup - automated backup and database (DB) snapshot. The difference is explained here. However, I am still confused: should I stick to automated backup only or both automated and manual (db snapshots)?

What do you think guys? What's the setup of your own? I heard from others that automated backup is not reliable due to some unrecoverable database when the DB instance is crashed so the DB snapshots are the way to rescue you. If I am to do daily DB snapshots as similar settings to automated backup, I am gonna pay much bunch of bucks.

Hope anyone could enlighten me or advise me the right set up.

Mysql Solutions


Solution 1 - Mysql

From personal experience, I recommend doing both. I have the automated backup set to 8 days, and then I also have a script that will take a snapshot once per day and delete snapshots older than 7 days. The reason is because from what I understand, there are certain situations where you could not restore from the automated backup. For example, if you accidentally deleted your RDS instance and did not take a final snapshot, you would not be able to access the automated backups that were done. But it is also good to have the automated backups turned on because that will provide you the point-in-time restore.

Hope this helps.

EDIT

To answer your comment, I use a certain naming convention when my script creates the snapshots. Something like:

autosnap-instancename-2012-03-23

When it goes to do the cleanup, it retrieves all the snapshots, looks for that naming convention, parses the date, and deletes any older than a certain date.

I think you could also look at the snapshot creation date, but this is just how I ended up doing it.

Solution 2 - Mysql

Just from personal experience, yesterday I accidentally deleted a table and had to restore from an RDS snapshot. The latest snapshot was only 10 minutes old, which was perfect. However, Amazon RDS took about 3 hours to get the snapshot online, during which time, the affected section of our site was completely offline.

So if you need to make a very quick recovery, do NOT depend on RDS backups.

Keep in mind, you can't download your snapshot so that you could view a database dump. Your only option is to wait for it to load in to a new database instance. So if you're only looking to restore a single table, RDS backups can make it a very painful process.

No blame to Amazon on this- they are awesome. But just something to keep in mind when planning, because it was a learning experience for us.

Solution 3 - Mysql

There are some situations where an automated backup does not recover the specific table you want to recover even though it has a point-in-time recovery feature. I am suggesting you enable the Backtracking feature for this kind of recovery and You can use "AWS-Backup" service to manage backups of Amazon RDS DB instances. Backups managed by AWS Backup are considered manual DB snapshots. Also, you will be required to keep automated backup enabled for creating read-replica for DB-instance in order to improve read performance. The retention period for automated backup should be between 1 and 35 so you can keep it a minimum of 1 day.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionJames WiseView Question on Stackoverflow
Solution 1 - MysqlBigJoe714View Answer on Stackoverflow
Solution 2 - MysqlHenry WeberView Answer on Stackoverflow
Solution 3 - MysqlVikk_KingView Answer on Stackoverflow