T-SQL Tuesday is a monthly event on the second Tuesday of each month; various SQL Server bloggers write about a specific topic, and *you* can join the party. This month’s topic was chosen by Allen Kinsel (blog|twitter), is “Disasters & Recovery”. If you have a story, then go to Allen’s blog and follow the instructions.
DR – All Done.
OK, your DR environment is all set up. And that’s it, job done, right?
Wrong. If you have never tested the DR environment, how do you know it works? I remember working at one place where they had got their DR office environment set up, and went for an exercise – try to fire up the DR site. Much of that exercise was spent just working out exactly which software installation media and licence keys were required! The second time they went for a run, they spent most of their time just making sure that they could get the Active Directory up & running – and they still hadn’t got any DR exercise as far as requiring my involvement in the time I was there.
Make sure you periodically test your DR. Make sure that your off-site safe stash of disks, licences etc are kept up-to-date. Make sure that you have a copy of your build documentation there. Make sure you can get access to this site as & when you need.
Practice makes perfect. But even when you’ve practised DR until you’re blue in the face, there’s always something missing compared with reality – and that’s the disaster itself, and the psychological & physiological impacts of working under that kind of stress.
DR for DR
For those of you that run their own DR site / environment, then (as well as practising the DR process), you might want to think about this – what if the DR systems themselves fail? Just a thought…