On Friday, we were asked to review a technical problem a neighbour was experiencing. It turned out that a MySQL server had somehow corrupted its data-file during a power-cycle. Although the user thought they had been backing up their data, what was actually being saved was a snapshot of their database from 2007. The upshot being that their database - in daily use since 2007 - was now hosed. The more the system was investigated, the greater the probability that their data was lost for ever. While it is embarrassing to lose your database, to lose it because your backup was useless is verging on the criminal. Laugh or snigger if you want but before you do, make sure

  1. you have a backup strategy
  2. and a disaster recovery plan
  3. and most important of all, make sure they all do what they are supposed to do

A couple of years ago, a few of our core servers were running on rather old hardware and were regularly subjected to quite serious levels of stress. Not surprisingly over a period of a couple of years we had a succession of disk failures. Fortunately we were able to recover within half-a-day after calamitous failures. Nothing like a real-world test to keep you on your toes. Nothing like a real-world example to remind you how wrong things can get!

This blog post was posted to Technobabble on Thursday February 3rd, 2011 at 4:05PM
 

Leave a Comment

All comments are moderated and hidden until reviewed; please preview before posting. You can use bbcode in the comment: e.g. [b]This is bold[/b], [url]http://www.willmcgugan.com[/url], [code python]import this[/code]
Preview Posting...
Previewing comment, please wait a moment...
Search for Posts
Tags
 
Popular Tags
 
Archives
2014
 
Recent Comments
As you mention, it is true that an unregistered record cannot be used in the (Select *) method of setting ...
 
© 2013 Andy Ferguson