PHP App Engine

http://www.tarsnap.com/

Online backups for the truly paranoid

At the present time, tarsnap does not support Windows (except via Cygwin) and does not have a graphical user interface.

http://www.jayhaabee.nl/blog/?p=43

For my first useful experiment with Amazon Elastic Cloud Computing (EC2 for short), I choose remote backup. Simply put, we’ll write a simple script, that fires up an Amazon EC2 instance, attaches a storage device and sync my valuable data to the Amazon EC2 device. Oh, and lets not forget to shutdown the EC2 instance to save us some money.

http://www.cenolan.com/2008/12/how-to-incremental-daily-backups-amazon-s3-duplicity/#more-54

This guide shows how to use Amazon S3 with duplicity to make secure GPG encrypted automated daily incremental backups (snapshots) of a Linux server or desktop. I have been using this method on various servers for several months and it has proved to be a reliable, secure, cheap, and robust method to create automated backups.

I have used this method on Fedora, YDL, and CentOS but the instructions should equally apply to other Linux distributions including Debian and Ubuntu. It will even work on OS X using the MacPorts version of duplicity.

http://github.com/truthtrap/ec2-elastic-backups

i put together these 2 files because i wanted dirvish like backups, but with snapshots and not too much work. all in all
it took me still to much, but thanks to tools like simpledb (http://code.google.com/p/amazon-simpledb-cli/) and the
wonderful amazon aws tools i have what i want.

http://www.techkismet.com/systems-admin/automating-ec2-ebs-snapshot-cleanup.html

So the problem in a nutshell is I have 10 volumes, each of which is cron’ed to be snapshotted at various times of the day (depends on the specific volume as to how often it is backed up). With 10 volumes, my S3 storage costs can get out of hand quite quickly. So I needed to develop a set of scripts that would scan my snapshots – and remove the oldest ones – so I’m not paying for that storage.

http://www.s3rsync.com/index.php/Rsync_to_Amazon_S3

The problem:
S3 storage protocol is “all or nothing” meaning that you can not modify a file on S3 and even for a minor change you have to upload (S3 PUT) the whole file again. This implies that backup and synchronization to S3 are inefficient. Any file modification forces you to upload the whole new file again, not just what was changed. So you are wasting bandwidth and the backup process is significantly slower!

Our solution:
S3rsync resolves this limitation and allows you to use Rsync bandwidth efficient algorithm that enables to upload only partial files that were changed. This is done by connecting to our Rsync servers located inside Amazon facility (Ec2). Using this functionality enables you to fully benefit from Rsync power.

http://www.floydprice.com/2009/10/automatic-elastic-block-snapshots-with-a-cron-job/

Amazon EC2 really is amazing, and the Elastic Block storage is pretty darn good too, however I wish you could automate the snapshot process form the EC2 console.

Before you start make sure you have a JRE:

http://blog.labnotes.org/2009/10/13/mysql-backups-with-ebs-snapshots/

Amazon EBS snapshots are awesome. You can take snapshots to backup your database, quickly move data between staging and production, run analytics on the latest data, resize volumes and much more.

For Apartly, I’m using MySQL, storing data and log files on a mounted EBS volume. EBS offers persistent, reliable storage (with replication for fault tolerance). Still, nothing can prevent data from disappearing, hence backups.

http://kovshenin.com/archives/cloud-tips-automatic-backups-to-s3/

In a previous post about backing up EC2 MySQL to an Amazon S3 bucket we covered dumping MySQL datasets, compressing them and uploading to S3. After a few weeks test-driving the shell script, I came up with a new version that checks, fixes and optimizes all tables before generating the dump. This is pretty important as mysqldump will fail on whatever step would cause an error (data corruption, crashed tables, etc), thus your uploaded to S3 archive would be kind of corrupt. Here’s the script: