• Having your CV up to date should always be part of your DR strategy!!!! . Even if you recover things, it may not be quick enough or your boss may decide to throw you (beep beep) in front of the bus to allowing any downtime.

    I don't mean to say that you shouldn't consider disasters, but the percentage of time these will happen, the true loss in $$ of downtime, etc have to be weighed. For Amazon.com, a few minutes of downtime are some serious $$, but only on the Internet for their retail systems. I'd bet that a day of downtime in their HR system wouldn't truly affect the company. Heck, their email may be down now due to the current MyDoom worm for all we know.

    I think the two posts above are worth reading again. You really have to assess the true business impact. Don't let anyone tell you that a day of downtime is more serious than it is, look back, see when you've been down and the impacts and make a smart decision. For most DR plans in most companies, the cost of the solution isn't worth it.

    But be sure that you do test your cheap and easy solutions, test restores, be sure you know where media is, have copies of CD keys somewhere (preferebly offsite), have phone numbers handy, vendor numbers, support contracts, etc.

     

    As far as the Internet goes, I haven't seen much in the way of planning docuements. Like many things, companies seem to consider this proprietary (I guess it could be used for an attacK) and not enough is published. Maybe we can get James to start a discussions