First, I'm a big believer that you need a paper copy of your DR plan somewhere - for every single client. Yes - you will probably have access to an electronic version. But realistically, in a true disaster, you may not have electricity. Or a building. So you need to know that you can get to the DRP even if the server's under water.
Second, you should not plan to replace the network exactly as it is today. Today's data and databases are much more flexible than in years gone by. So plan to get the newest, best equipment and software you can. Having said that, if you have some old line of business application, you may need some older technology to make that work. Make sure that's in your plan!
Of course, the more you rely on the cloud, the fewer disasters you'll have and the easier it is to get back up.
The 800 pound gorilla for disaster recovery is the BDR - backup and disaster recovery system. This will allow you to move quickly into "business continuity" mode rather than disaster mode.
Here are a few specific things to keep in mind:
1. Go slow. Don't rush around and freak out. First, assess the actual damages, determine what the most recent successful backup is, and what resources you have available to you.
2. Make a plan! Yes you have the big DR Plan. But now you need to create a specific plan for this specific disaster. What will you do first? What will you do second? etc.
3. Use a TSR Log. I've covered this many times. Here's a specific post: http://blog.smallbizthoughts.com/2011/07/sop-friday-troubleshooting-and-repair.html
4. Update the plan! How could it have gone better? How can you improve the process? And is it possible to avoid this disaster altogether next time?
Hope that helps.
Add your best tips below.
Post a Comment
Please note, however, that spam will be deleted, as will abusive posts.