On Thu, Jun 24, 2010 at 11:22 AM, Jay Dale <[email protected]> wrote: > I’ve been assigned to create a DR plan for our company ...
http://i.zdnet.com/blogs/dilbert_disaster_recovery_plan.jpg > I’ve never actually had to come up with one before. There's two major parts, the analysis/cost planning part, and the technical/procedural planning part. The basics of analysis are: A1. Identify resources A2. Obtain figures for what non-availability of each resource costs A3. Identify threats to resources (such as disk failure, building fire, etc.) A4. Identify possible counter-measures for each threat, and costs of same A5. Compare cost of downtime with cost of counter-measures, taking into account the likelihood of each threat. This tells you what counter-measures are worth it to your situation. Planning the technical/procedural is also conceptually simple: B1. Figure out how to do what you decided on in A5 (read the manual, etc.) B2. Write everything from B1 down B3. Test everything in B2 B4. Take what you learned in B3 and apply it to B2; repeat B2 and B2 as needed B5. Once you've got a good plan, practice it periodically B6. Keep an eye on everything and repeat all steps as needed The devil is in the details, as usual. Entire shelves worth of books have been written on the subject. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
