Steve Lacey. Get yours at flagrantdisregard.com/flickr

Backups Moved To Amazon S3

| | Comments (3) | TrackBacks (0)

Previously, I’ve been backing up all the irreplaceable household data (movies, photos, etc…) to my colo’d server using Scott Ludwig’s most excellent Link-Backup script.

Unfortunately I’ve been running out of space on that server and am thinking about decommissioning it, so as the first step of the decommission I need to move my offsite backups somewhere else. The obvious place appears to be Amazon’s S3 service as the price of storage seems very cheap - $0.15 per gigabyte. There are also transfer charges, but in the general case it’s upload only, so I’m ignoring that. I have about 100GB to store, which works out at $15 per month.

Very reasonable.

The next thing to figure out is “how do I perform the backup?” I initially thought that the easiest thing to do would be to continue to use Link-Backup. All I need to do is bring up and EC2 instance every time I need to backup and then use Link-Backup as I had been doing previously.

The big problem with this was that bringing up an instance is not trivial. Relatively simple, but not trivial. Also, the EC2 tools require Java 1.5 to run and it’s not available on PPC Debian linux. Sigh.

I then dig a search around and found Jeremy Zawodny’s excellent blog post on the subject which provides a nice roundup of the available solutions. I decided to go with the ruby based s3sync.

Set up was pretty simple. I first created an AWS account, collected the required data and configured s3sync. I then created some scripts as suggested by John Eberly and I was off to the races!

I ran some tests to make sure I could:

  1. Backup a small directory that had some hierarchy in it.
  2. Restore that directory.
  3. Make some small changes to the local directory and make sure that only the changes were synced.
  4. Pull back a single file using the included s3cmd script.

It all worked perfectly, so now I have ~70GB of photos syncing up to S3.

Sweet!

Next steps:

  1. Add everything else (home movies, etc…) to the backup
  2. Rebuild my little webapp using Google’s AppEngine.
  3. Move my blogs somewhere else (maybe Media Temple - an opinions? I need to run MovableType and MySql).
  4. Decommission server.
  5. Use saved cash to buy more toys.

Sounds like a plan.

0 TrackBacks

Listed below are links to blogs that reference this entry: Backups Moved To Amazon S3.

TrackBack URL for this entry: http://www.steve-lacey.com/cgi-bin/mt/mt-bar.cgi/1121

3 Comments

Colin Meeks said:

Hi Steve. You might want to look at Mozy:
http://www.mozy.com

I looked at S3, but with nearly 200 gig of stuff, it was going to end up expensive. Mozy is $5 per month, with unlimited storage. Only problem is getting all 200gig there, it's been running over a week and I've just tipped the 50% mark. Nice cheap fallback though. I still use S3, but just for programming code and documents.

Colin

Jeff Barr said:

Hi Steve, great post!

You can use the Elastic Fox extension for Firefox to launch EC2 instances from within a comfortable GUI environment.

I am running the EC2 tools with JRE 1.6.0.05 and they seem to work just fine.


Ryan Grove said:

Mozy's restore process is seriously broken. I recommend avoiding them. Before assuming that your data is safe, try doing a test restore; I learned that the hard way.

Leave a comment

About Me

Steve Lacey, software developer at Facebook, British, married to the lurvely Nabila, dad to the wonderful Julian and Jasmine. Living in Kirkland (near Seattle), WA.


A brief professional bio.


steve@steve-lacey.com
+1 (425) 214-4716

About this Entry

This page contains a single entry by Steve published on April 13, 2008 6:08 PM.

A Couple Of Great TED Videos was the previous entry in this blog.

Persistent Storage for Amazon EC2 Services is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Statsorama

  • 1050 posts
  • 1333 comments

Music