2008-03-14 #1

Redundant MySQL set-up for Amazon EC2

• http://info.rightscale.com/2007/08/20/redundant-mysql
• http://info-architects.net/2007/08/25/rake-task-for-mysql-backup-to-amazon-s3/
• http://paulstamatiou.com/2007/07/29/how-to-bulletproof-server-backups-with-amazon-s3
• http://elliottback.com/wp/archives/2007/08/05/easy-database-backup-with-amazon-s3/
• http://wiki.zmanda.com/index.php/How_To:Backup_to_Amazon_S3

Your application will execute on a virtual computer that we call an instance. You have the choice of several instance types, allowing you to select a configuration of memory, CPU, and instance storage that is optimal for your application:

Small Instance:

1.7 GB of memory, 1 EC2 Compute Unit (1 virtual cores with 1 EC2 Compute Unit), 160 GB of instance storage, 32-bit platform $0.10 per instance-hour consumed or partial hour consumed

Large Instance:

7.5 GB of memory, 4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each), 850 GB of instance storage, 64-bit platform $0.40 per instance-hour consumed or partial hour consumed

Extra Large Instance:

15 GB of memory, 8 EC2 Compute Units (4 virtual cores with 2 EC2 Compute Units each), 1690 GB of instance storage, 64-bit platform $0.80 per instance-hour consumed or partial hour consumed

See Amazon EC2 Instance Types for details on available configurations. You have full and exclusive access to an instance once you have commissioned it.

use Linux Volume manager snapshots to back-up the DB to Amazon S3