All the Perl that's Practical to Extract and Report

Navigation

use Perl Log In

acme (189)

acme (email not shown publicly)http://www.astray.com/Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.

Amazon Web Services

It was quite short notice (and on a Saturday!) but Jeff Barr presented a talk on Amazon Web Services to London.pm yesterday. It was a good run through the many services that Amazon can provide to programmers. Many people were convinced to back photos up to S3 instead of tape and were intrigued by the compute cloud. Recently I have been saying that I'm mostly IO-bound, not CPU-bound, but I realise I've been wrong: with EC2 and S3 the balance changes. I have some ideas and I'll benchmark some interesting things later on. Thanks Jeff!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

At the moment I'd say the tools aren't entirely there. I do quite like http://www.rjonna.com/ext/s3fox.php [rjonna.com] for inspecting S3 but otherwise it's not amazing. I just knocked up something which uses Net::Amazon::S3.

S3Backup (http://s3backup.blogspot.com/) is one possible answer, but only available for Linux and Windows.
Jungle Disk (http://www.jungledisk.com/) is another. My plan is to see if I can make that work with Adobe Lightroom's library feature, so I can search my archive locally, but pull the images from S3 if I need them.
- Neil.

The difference being that rsnapshot doesn't come with bundled enterprise grade disaster planning.The main reason I'm interested in S3 is I'm a shit sysadmin who avoids having to control my own physical resources, and if Amazon trusts S3 enough to put their OWN data inside of it, then I'm willing to slap an "Enterprise-Grade Backup" mental sticker on it and trust it with my stuff too.

That's not to say I necesarily trust them to keep it always secret (although Brackup might go a bit far to prevent it in that

I used to be all paranoid about how safe my backups were. Then I realised that if my house burns down, I've got bigger things to worry about than the fact that I didn't have backups safely squirrelled away on another continent.