Thank you, Steve, for this warning. It reminds me of when I first had a brush with a disaster and trying to recover from it. It was fairly early in my time at my last job. My boss, who had run the network, servers, databases, etc., had left for a job out of state. I was left with having to handle everything, since I was the senior member of the team. Up to that point I'd never managed networking, servers, etc. I had only been a developer. Things went well for several months until the building we were in had a lightening strike. No one knew it before the lightening strike but the building was not properly wired for disasters like that. It shut everything down and took out our email server. Believe me, we were not prepared for that. I was not prepared for that. Fortunately I was in very good physical shape at the time, as I believe if I hadn't been I would have experienced a heart attack, due to the stress. We eventually got everything up and running again, with a new email server. And that was my introduction to DR. Until that point, I'd ever even heard of the term.
Well, Rod, at least that wasn't directly your fault. Back in the days of flat files before databases and transaction logs, my worst move was deleting the wrong file and losing a production master Open Order file which was used for manual and dial-up data entry 24 hours a day. And there was no 'recycle bin' then either. I caused several hours of research and re-entry of data from union labor data-entry folk and telephone customer service people, while a warehouse shift of union workers waited unable to prepare orders, then went on overtime to catch up so trucks could leave.
Rick
Disaster Recovery = Backup ( Backup ( Your Backup ) )