Three Principles of Practical Business Recovery
it in – don’t add it on
business recovery – don’t implement it
test, test – don’t just plan, plan, plan
Build It In – During Design Phase
(hardware and software)
uses for as much as possible
Adopt – Don’t Just Implement
knowledge spread among many
hate change – but they will do it when it makes sense to them
all critical material ( Yes, all )
costs can have big impact
home connectivity for critical users
Testing is Better Than Planning
Proposal from Recovery Consulting Vendors:
complex plan – many books (that sit on a shelf, unread and unused)
(when you can)
many smaller distributed plans.
often – very often.
using the actual people who will (or may) recover.
Plans Are Necessary
to have a tested plan that has been used
than to have a more robust plan
that no one reads
small plans are better
is an issue
Testing is Absolutely Necessary
actual people doing actual tasks
at least annual; semi-annual is better
errors are good in tests
a map – I’ve been there
know the server works – I use it every week
know how to use server based systems – I did it last month
Testing The Site
at least once annually
when there are major changes
people do real tasks: e.g.
documentation of critical processes
cross training to reduce “failure” points
dispersion of trained people
separation helps, but it’s not sufficient
This Consultant Note is a summary of the approach we use to help improve the implementation and effectiveness of business recovery / disaster planning initiatives. To help you achieve better payoff from your business recovery operation, contact us or email to email@example.com.
Some of the material in this Note was originally presented at the annual meeting of the Information Systems Management Forum in Tampa, Florida, December 2001.
© Copyright 2002-2003, Christopher Technology Consulting LLC