Home / server / Questions / 559984
In Process
Rich Bradshaw
Asked: 2013-12-09 06:38:21 +0800 CST

How best to structure Glacier backups?

  • 772

I'm planning to back up multiple websites to Glacier at midnight each day.

My current system is to create a tar.gz of the whole of /var/www (i.e. all the sites), and to copy that to a different server.

I'm assuming I would use these backups if the whole server failed, though perhaps I'd occasionally want to retrieve individual files.

Should I continue in the same way (tar.gz of all per day in one Vault), or have different tar.gz per site in the same vault, or different tar.gz per site each in a vault per site?

amazon-glacier

1 Answers

  1. The "best of both worlds" approach would be the following:

    1. Create a S3 bucket for backups
    2. Configure a lifecycle rule, so items older than 2 weeks (for example) are automatically transitioned to Glacier class storage.
    3. Plan your backups as simple file syncing tasks using S3 for destination. You have plenty of tools to automate this.

    By doing it this way, you will have a decent "instantly ready" backup in S3 for the last weeks, with much more advanced copy tools (sorry, Glacier) and you will benefit from the lower costs of Glacier and the S3 interface to retrieve items, much friendlier than Glacier's.

    • 2