BKPDRPIT.RVW   20060823

"A Primer for Disaster Recovery Planning in an IT Environment",
Charlotte J. Hiatt, 2000, 1-878-28981-0
%A   Charlotte J. Hiatt
%C   1331 E. Chocolate Ave., Hershey, PA   17033-1117
%D   2000
%G   1-878-28981-0
%I   IRM Press/Idea Group
%O   800-345-432 717-533-8845 fax: 717-533-8661 cust@idea-group.com
%O  http://www.amazon.com/exec/obidos/ASIN/1878289810/robsladesinterne
  http://www.amazon.co.uk/exec/obidos/ASIN/1878289810/robsladesinte-21
%O   http://www.amazon.ca/exec/obidos/ASIN/1878289810/robsladesin03-20
%O   Audience a Tech 1 Writing 2 (see revfaq.htm for explanation)
%P   276 p.
%T   "A Primer for Disaster Recovery Planning in an IT Environment"

It is interesting to note that the introduction says nothing about the
purpose of the book (and does suggest that those planning for disaster
recovery can benefit from bringing in consultants).

There are several oddities in this work.  The chapters are not
numbered, and most are very short.  The Appendices (mostly forms) are
longer than the text of the book itself.

The chapters cover topics such as a definition of a disaster (which
doesn't define so much as lay out categories), examples of disasters,
statistics supporting the need for disaster planning, a recommendation
to obtain management support, a terse list of the composition of the
planning team, desirable characteristics of the team coordinator, risk
and business impact analysis (good as far as it goes, but fairly
standard), options for offsite data storage, and system recovery
options.  The book suggests evaluating alternatives for plan
development (including the aforementioned consultants) and defining
the assumptions and limits of the strategy.  (The components that go
into the written plan gets more space than the procedures for
emergency response.)  Emergency management, disaster recovery teams, a
notification directory, emergency operations centre, training,
testing, maintenance, invocation, and media management all get
relatively brief overviews.  The book also lists other resources and
references.

While the material is fundamentally sound, it is neither extensive nor
particularly related to information technology as such.  Details of
options and alternatives are scant.  This is certainly a worthwhile
reference as a reminder for anyone involved in disaster recovery
planning, and as a guide for the process.  For those dealing
specifically with contingency plans for computer system operations,
additional resources will be required.

copyright Robert M. Slade, 2006   BKPDRPIT.RVW   20060823