Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

February Question: Share with us your “best” restore disaster stories.

As DBAs, making backups and restoring data is one of the foundational skills we all must master. But sometimes things go wrong, very, very wrong. And it is from these mistakes that we often learn important lessons. This month, the Question of the Month is, “Share with us your ‘best’ restore disaster stories.” Tell us stories about yourself, or from others you know, where restores went bad, very, very bad.

Post your responses to the above SQL Server Question of the Month in the comments section below (or at www.bradmcgehee.com if you are viewing this from a syndicated newsfeed). And don’t forget to enter your e-mail address when you post your response, so I can contact you if you win.

Because there is no right or wrong answer, this month’s winner will be selected randomly from all the entries that are received.

This Month’s Prizes

SQL Backup and Restore Bundle

The prizes this month are an Amazon.com voucher worth US$50.00, and a license for a SQL Backup and Restore Bundle, with one year of support and upgrades. The SQL Backup and Restore Bundle is the complete package for faster, stronger backups and restores, and includes two high-performance backup tools (SQL Backup and SQL HyperBac) and SQL Virtual Restore. To find out more, visit the Red Gate website.

Comments

Posted by sreddy on 3 February 2011

Hey Brad,

Paul Randal might be the best source for some horrific disaster stories. :) I attended one of his sessions at the Pass Summit a couple of years ago on how to plan your recovery strategy, and I've hopefully learned from his clients' horror stories - one client I believe had a full backup and several months(5?) worth of hourly log backups that had to be restored after a disaster... Since then, I've beefed up the backups: a weekly full + daily differential + more than once-hourly log back ups, a daily copy-only backup and two replicated databases of the production database.  Possibly overkill, but when a business' life blood is the database - can't afford to say "oops... sorry!".  The copy-only backups get restored pretty often (testing my backups) and one replicated database is heavily used - so hopefully won't have to post a my own disaster story anytime soon... thanks for blogging, Smitha

Leave a Comment

Please register or log in to leave a comment.