ITSM Service Continuity Methods and Best Practices
The disaster recovery planning methodology consists of many disaster recovery planning processes. The contemplated disaster recovery planning effort, which will be performed after the disaster recovery business impact analysis, will be accomplished utilizing the disaster recovery planning processes, which are summarized below.

Please note that the sections on Application Inventory and Criticality Ratings, Critical Application System Resource Requirements, and Alternate Processing Strategies are partly covered in a business impact analysis, but are included here for completeness.

Important ITSM Service Continuity Information Areas (1-7 of 14)
     1) Overview - The overview is the first step addressed in the disaster recovery planning process. The project boundaries (purpose, scope, objectives and assumptions) to be used in developing the disaster recovery plan should be defined, documented, and approved by management. The types of disasters addressed by the disaster recovery plan will depend upon the physical location of the company and its information processing facilities.
     2) Application Inventory and Criticality Ratings - In a business impact analysis, all application systems are identified and categorized as to their criticality relative to the continuation of the business operations. To define the criticality and recovery sequence of an application system, its major functions, size and complexity, impact on other systems, and processing schedule should be taken into consideration. Processing of critical systems should be resumed as quickly as possible after a disaster. Less critical systems should be processed as soon as possible after data processing operations are restored or if time and resources are available, after restoration of critical systems. Non-critical systems should be restored when data processing services are available.
     3) Disaster Recovery Teams - Establishment of functional teams and identification of individuals is necessary to assure preparedness in the event of a disaster. Designating personnel to be responsible for specific functions before, during and after an emergency situation is essential to assure that the proper actions will be taken expeditiously. Team members must participate in the disaster recovery planning process to assure that responsibilities and roles are defined, documented, assigned to specific individuals, understood, executable and accurately represent what is required for a successful recovery.
     4) Off-Site Backups - The required off-site movement of software, associated data, documentation, and any additional resources needed in the event of a disaster should be identified, documented and implemented. The backup scheme used should respond effectively to the most likely problem situations while still providing a tolerable solution in major recovery situations. Criticality and execution frequency of each application system will determine the frequency of backup and the safeguards designed into the backup scheme.
     5) Critical Application System Resource Requirements - Once critical systems have been identified and restoration sequences defined, the resource requirements needed to process each critical system must be determined. The resource and processing requirements identified for all critical systems are analyzed in the recovery and alternate processing strategies process to determine the minimum resource requirements and configuration (hardware, software, communications, forms, supplies, special equipment, etc.) required to process all critical systems in the event of a disaster.
     6) Alternate Processing Strategies and Inventories Required - The overall recovery strategy and listings of the hardware, software, telecommunications, support equipment, forms, supplies, etc. needed in the event of a disaster must be identified and documented. The recovery strategies to be used in the event of a disaster should be based upon a summary of the requirements and resources identified for each critical system. The strategy decision must be unique to the particular company and situation. Seldom will a single strategy be the optimum solution. For instance, a single strategy for disaster critical applications might be considered, with reduction or withdrawal of services for less critical or non-critical applications.
     7) Operating Procedures - The capability to recover from both major and minor disasters necessitates the availability of a comprehensive set of operating procedures describing the steps required to re-establish data processing in the event of a disaster. Therefore, the documentation required should consider the various levels of disasters that could occur and support the objectives, assumptions and strategies of the Disaster Recovery Plan. Operating procedures can be incorporated either in the disaster recovery plan, or separately with a reference note in the disaster recovery plan. The procedures must be available to technical support and operations personnel with a current copy placed in the off-site vault. The procedures needed to recover from a disaster will be specific for the actual restorations and, in most instances, for normal processing will be the same as those used in daily operations. Existing procedures should be used where possible to satisfy disaster planning documentation requirements. This will minimize the effort necessary to produce procedures and the training of personnel in the recovery process. Disaster recovery procedures should be tested periodically and also modified as changes in the data processing facility and environment occur.

In the next Newsletter we will finalize the 14 necessary components and steps to developing an effective ITSM Service Continuity, Disaster Recovery Plan