Backup strategy through DO + Off-site

October 14, 2014 1.2k views

Hi - I have a question after reading the article about choosing an effective backup strategy.

I currently have backups enabled for my droplets. Furthermore, I configured AutoMySQLBackup on these droplets so MySQL Dumps are being captured within the file system. I am aware of the two major flaws of DO backups that currently exist: (1) you cannot download backups for the purpose of extracting specific files and (2) they are not run daily but rather every few days. It is my understanding that both of these flaws are in the process of being fixed.

It seems as if off-site backups via Rsync, Bacula, BackupPC, or Duplicity are also recommended. My question is why? The automated backups are sent to Amazon Glacier so isn't that considered off-site? In the worst case scenario where my droplet becomes completely unusable, couldn't I create a new droplet from a backup that was taken by DO which now resides in Amazon Glacier and then extract whatever files I needed and/or rebuild a droplet that way?

I guess I'm trying to understand the scenario where the DO backup would not be sufficient and an off-site backup via Rsync, Bacula, BackupPC, or Duplicity would be. Additionally, where are some good / cheap / secure places to store such backups?


1 Answer

I can think of one scenario:

Due to a credit-card glitch, your Digital Ocean account is cancelled and you are unable to login. Fortunately, you have complete backups in a place that is not related to Digital Ocean, so you are able to retrieve all of your web-files and MySQL dumps.

Or (not likely) Digital Ocean suddenly goes belly-up and all accounts are suddenly closed...

I use rsync and DreamObjects to back up all website files, MySQL dumps, SSH keys, and custom scripts...on a daily basis as well as a monthly basis.

Sometimes, if I am working on a project, I will set hourly backups.

I have never regretted having too many backups.

Have another answer? Share your knowledge.