Cloud Zone is brought to you in partnership with:

Avi is a DZone MVB and is not an employee of DZone and has posted 16 posts at DZone. You can read more from them at their website. View Full User Profile

Infographic: MySQL Disasters in the Cloud

03.21.2013
| 10641 views |
  • submit to reddit

Curator's Note: The content of this article was originally written by Avigail Ofer on the Xeround blog.

Anyone who works with databases knows how critical they are to business operations, and how bad it can be when something goes wrong. Millions of individuals and organizations worldwide depend on MySQL, and no one is immune to downtime and data loss – even venerable organizations such as Amazon Web Services, Github and Percona have experienced catastrophic failure of MySQL databases.

  • Interested in seeing the biggest MySQL “earthquakes” of all time? The infographic below tells their stories, including the lessons learned after each database failure, from reputable sources including Wired, Slashdot, TechCrunch and ZDNet.
  • Did you know that data loss and corruption accounts for only 10% of MySQL failures? The rest are due to hardware/OS, performance and replication issues. See this and other interesting statistics further down in our infographic. Data was taken from Percona’s MySQL Failure Causes White Paper.
  • Deleted your InnoDB data file? Don’t worry, you can probably recover it. See this and 7 other common causes of MySQL failure, and how to recover or prevent them altogether. This last part of our infographic was based on Ronald Bradford‘s classic book, Effective MySQL Backup and Recovery.

Here at Xeround, we make MySQL more reliable with a cloud database service that guarantees high availability (even during Amazon outages!) and automatic elasticity with no downtime or application changes. If you want to try disaster-free MySQL on the cloud, create your free database now!


(Click to enlarge infographic)





Published at DZone with permission of Avi Kapuya, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)