Workbook 3 : Disaster Recovery In Complex Networks
LEARN HOW TO:
How an organisation can get its critical applications functioning sufficiently quickly to avert a major and irreversible disaster.
How to prepare an IT environment so that it can be recovered in the event of a disaster.
How to identify and rationalise the processes and complexities which are involved in writing a plan.
How to avoid the effect of queued non critical applications becoming critical because of the time lag.
How to prioritise and recover databases held on distributed file servers.
WORKBOOK OBJECTIVES:
Organisations who have large and distributed networks often do not have a recovery plan. One of the reasons is the complexity involved in designing and writing a plan and the feeling that with a distributed system they will not lose all their processing power at one time. Yet, "Statistics indicate that 80% of companies who suffer a major disaster, and do not have any form of continuity of contingency capability go into liquidation within 18 months". Graham Heath, Director of Norwich Union Risk services How organisations can avoid this situation is examined in this workbook.
The essential need of diaster recovery success is to use all the organisation's key human resources to write the plan, how this can be accomplished is also discussed, as are ways to win line management and user cooperation in designing and evaluating the plan. The costed plan then needs to be written and cooperation is needed for this so that a central editing team can produce the finished document, again methods for achieving this end are discussed.
Testing is covered together with the pitfalls. How staff can be encouraged to cooperate and give useful feed back to the Disaster Coordinator is examined as well as methodologies for acceptably updating the plan in the light of the test. Once written and tested the plan has other uses and these are examined, as are real life disasters, to ensure that all aspects of recovery are considered.
WHO SHOULD USE THIS WORKBOOK:
Workbook is targeted for anyone concerned with the integrity and availability of a business function that operates through a network of computers.
