All data (except image files) is stored in a MySQL database and mirrored through a master/slave setup to another database on a different computer. The Slave MySQL data is stored in an AWS EBS volume. The EBS volume is automatically replicated within the same Availability Zone. This prevents data loss due to failure of any single hardware component. This means that there are two copies of all data (except image files) on two different machines (and replicated!) at all times.
All data (including image files) is backed up nightly to S3 buckets in a data center on the west coast. So while the servers and data are in a data center on the east coast, the backups are on the west coast. So even if the east coast gets sucked into the ocean (which we really really hope won't happen) , we can start everything right back up on the west coast. So how about that! And: We keep full daily copies of all data for one month.
Image file backups are stored in a separate S3 bucket - files are not deleted nor does the EntryThingy system have read or delete access to the backup bucket.
This is what Amazon says about the reliability of S3: "Amazon S3 gives any developer access to the same highly scalable, reliable, fast, inexpensive data storage infrastructure that Amazon uses to run its own global network of web sites. The service was designed for 99.99% availability..." - and "Amazon S3 uses proven cryptographic methods to authenticate users."
Did this answer your question?Thanks for the feedbackThere was a problem submitting your feedback. Please try again later.