Disaster Recovery Plan Sample

August 6, 2012 by Leave a Comment

The objective of a disaster recovery plan is to ensure that you can respond to a disaster or other emergency that affects information systems and minimize the effect on the operation of the business. When you have prepared the information described in this topic collection, store your document in a safe, accessible location off site.

You can download this Disaster Recovery Plan Sample for free using the links below:

Microsoft Word 97-2003: Click Here

Microsoft Word 2010: Click Here

Adobe PDF:  Click Here

Disaster Recovery Plan Sample

Section 1. Example: Major goals of a disaster recovery plan sample

 Here are the major goals of a disaster recovery plan.
  • To minimize interruptions to the normal operations.
  • To limit the extent of disruption and damage.
  • To minimize the economic impact of the interruption.
  • To establish alternative means of operation in advance.
  • To train personnel with emergency procedures.
  • To provide for smooth and rapid restoration of service.

Section 2. Example: Personnel

You can use the tables in this topic to record your data processing personnel. You can include a copy of the organization chart with your plan.
Data processing personnel
Name Position Address Telephone
Data processing personnel
Name Position Address Telephone
Data processing personnel
Name Position Address Telephone

Section 3. Example: Application profile

You can use the Display Software Resources (DSPSFWRSC) command to complete the table in this topic.
Application profile
Application name Critical Yes / No Fixed asset Yes / No Manufacturer Comments
Comment legend:

1.
Runs daily.
2.
Runs weekly on ____________.
3.
Runs monthly on ____________.

Section 4. Example: Inventory profile

You can use the Work with Hardware Products (WRKHDWPRD) command to complete the table in this topic.
Application profile
Manufacturer Description Model Serial number Own or leased Cost
Notes:

1.
This list should be audited every ____________ months.
2.
This list should include the following items:Processing units                        System printer
Disk units                                 Tape and optical devices
Models                                     Controllers
Workstation controllers              I/O Processors
Personal computers                   General data communication
Spare workstations                    Spare displays
Telephones                               Racks
Air conditioner or heater            Humidifier or dehumidifier
Miscellaneous inventory
Description Quantity Comments
Note: This list should include the following items:

Tapes                                                    CDs and DVDs
PC software                                          Emulation packages
File cabinet contents or documentation     Language software (such as COBOL and RPG)
Tape vault contents                                Printer supplies (such as paper and forms)
Optical media

Section 5. Information services backup procedures

Use these procedures for information services backup.
    • System i® environment
      • Daily, journals receivers are changed at ____________ and at ____________.
      • Daily, a saving of changed objects in the following libraries and directories is done at ____________:
        • ____________
        • ____________
        • ____________
        • ____________
        • ____________
        • ____________
        • ____________
        • ____________

        The preceding procedure also saves the journals and journal receivers.

      • On ____________ at ____________ a complete save of the system is done.
      • All save media is stored off-site in a vault at ____________ location.
    • Personal Computer
      • It is suggested that all personal computers be backed up. Copies of the personal computer files should be uploaded to the System i environment on ____________ (date) at ____________ (time), just before a complete save of the system is done. It is then saved with the normal system save procedure. This provides for a more secure backup of personal computer-related systems where a local area disaster can wipe out important personal computer systems.

Section 6. Disaster recovery procedures

For any disaster recovery plan, these three elements should be addressed.
  • Emergency response procedures
    • To document the appropriate emergency response to a fire, natural disaster, or any other activity in order to protect lives and limit damage.
  • Backup operations procedures
    To ensure that essential data processing operational tasks can be conducted after the disruption.
  • Recovery actions procedures

Section 7. Recovery plan for mobile site

This topic provides information about how to plan your recovery task at a mobile site.
    • Notify ____________ of the nature of the disaster and the need to select the mobile site plan.
    1. Confirm in writing the substance of the telephone notification to ____________ within 48 hours of the telephone notification.
    2. Confirm all needed backup media are available to load the backup machine.
    3. Prepare a purchase order to cover the use of backup equipment.
    4. Notify ____________ of plans for a trailer and its placement (on ____________ side of ____________).
    5. Depending on communication needs, notify telephone company (____________) of possible emergency line changes.
    6. Begin setting up power and communications at ____________.
      1. Power and communications are prearranged to hook into when trailer arrives.
      2. At the point where telephone lines come into the building (____________), break the current linkage to the administration controllers (____________). These lines are rerouted to lines going to the mobile site. They are linked to modems at the mobile site.The lines currently going from ____________ to ____________ would then be linked to the mobile unit via modems.
      3. This can conceivably require ____________ to redirect lines at ____________ complex to a more secure area in case of disaster.
    7. When the trailer arrives, plug into power and do necessary checks.
    8. Plug into the communications lines and do necessary checks.
    9. Begin loading system from backups.
    10. Begin normal operations as soon as possible:
      1. Daily jobs
      2. Daily saves
      3. Weekly saves
    11. Plan a schedule to back up the system in order to restore on a home-base computer when a site is available. (Use regular system backup procedures).
    12. Secure mobile site and distribute keys as required.
    13. Keep a maintenance log on mobile equipment.

Section 8. Recovery plan for hot site

An alternate hot site plan should provide for an alternative (backup) site. The alternate site has a backup system for temporary use while the home site is being reestablished.
    1. Notify ____________ of the nature of the disaster and of its desire for a hot site.
    2. Request air shipment of modems to ____________ for communications. (See ____________ for communications for the hot site.)
    3. Confirm in writing the telephone notification to ____________ within 48 hours of the telephone notification.
    4. Begin making necessary travel arrangements to the site for the operations team.
    5. Confirm that you have enough save media and that it is packed for shipment to restore on the backup system.
    6. Prepare a purchase order to cover the use of the backup system.
    7. Review the checklist for all necessary materials before departing to the hot site.
    8. Make sure that the disaster recovery team at the disaster site has the necessary information to begin restoring the site.
    9. Provide for travel expenses (cash advance).
    10. After arriving at the hot site, contact home base to establish communications procedures.
    11. Review materials brought to the hot site for completeness.
    12. Start to load the system from the save media.
    13. Begin normal operations as soon as possible:
      1. Daily jobs
      2. Daily saves
      3. Weekly saves
    14. Plan the schedule to back up the hot-site system in order to restore on the home-base computer.

Section 9. Restoring the entire system

You can learn how to restore the entire system.

  • To get your system back to the way it was before the disaster, use the procedures in Checklist 20: Recovering your entire system after a complete system loss.

    Before you begin: Find the following save media, equipment, and information from the on-site tape vault or the offsite storage location:

    • If you install from the alternate installation device, you need both your save media and the CD-ROM media containing the Licensed Internal Code.
    • All save media from the most recent complete save operation
    • The most recent save media from saving security data (SAVSECDTA or SAVSYS)
    • The most recent save media from saving your configuration, if necessary
    • All save media that contains journals and journal receivers that you saved since the most recent daily save operation
    • All save media from the most recent daily save operation
    • PTF list (stored with the most recent complete save media, weekly save media, or both)
    • Save media list from most recent complete save operation
    • Save media list from most recent weekly save operation
    • Save media list from daily saves
    • History log from the most recent complete save operation
    • History log from the most recent weekly save operation
    • History log from the daily save operations
    • The Installing, upgrading, or deleting i5/OS and related software PDF. You can order a printed version of this PDF (SC41-5120; feature code 8006) with i5/OS software upgrade orders or new hardware orders.
    • The Recovering your system PDF. You can order a printed version of this PDF (SC41-5304; feature code 8007) with i5/OS software upgrade orders or new hardware orders.
    • Telephone directory
    • Modem manual
    • Tool kit

Section 10. Rebuilding process

The management team must assess the damage and begin the reconstruction of a new data center.

  • If the original site must be restored or replaced, the following questions are some of the factors to consider:

    • What is the projected availability of all needed computer equipment?
    • Will it be more effective and efficient to upgrade the computer systems with newer equipment?
    • What is the estimated time needed for repairs or construction of the data site?
    • Is there an alternative site that more readily can be upgraded for computer purposes?

    After the decision to rebuild the data center has been made, go to Section 12. Disaster site rebuilding.

Section 11. Testing the disaster recovery plan

In successful contingency planning, it is important to test and evaluate the plan regularly.

  • Data processing operations are volatile in nature, resulting in frequent changes to equipment, programs, and documentation. These actions make it critical to consider the plan as a changing document.

    Table 1 should be helpful for conducting a recovery test.

    Table 1. Checklist for testing the disaster recovery plan
    Item Yes No Applicable Not applicable Comments
    Conducting a Recovery Test
    1. Select the purpose of the test. What aspects of the plan are being evaluated?
    2. Describe the objectives of the test. How will you measure successful achievement of the objectives?
    3. Meet with management and explain the test and objectives. Gain their agreement and support.
    4. Have management announce the test and the expected completion time.
    5. Collect test results at the end of the test period.
    6. Evaluate results. Was recovery successful? Why or why not?
    7. Determine the implications of the test results. Does successful recovery in a simple case imply successful recovery for all critical jobs in the tolerable outage period?
    8. Make suggestions for changes. Call for responses by a given date.
    9. Notify other areas of results. Include users and auditors.
    10. Change the disaster recovery plan manual as necessary.
    Areas to be tested
    1. Recovery of individual application systems by using files and documentation stored off-site.
    2. Reloading of system save media and performing an initial program load (IPL) by using files and documentation stored off-site.
    3. Ability to process on a different computer.
    4. Ability of management to determine priority of systems with limited processing.
    5. Ability to recover and process successfully without key people.
    6. Ability of the plan to clarify areas of responsibility and the chain of command.
    7. Effectiveness of security measures and security bypass procedures during the recovery period.
    8. Ability to accomplish emergency evacuation and basic first-aid responses.
    9. Ability of users of real time systems to cope with a temporary loss of online information.
    10. Ability of users to continue day-to-day operations without applications or jobs that are considered noncritical.
    11. Ability to contact the key people or their designated alternates quickly.
    12. Ability of data entry personnel to provide the input to critical systems by using alternate sites and different input media.
    13. Availability of peripheral equipment and processing, such as printers and scanners.
    14. Availability of support equipment, such as air conditioners and dehumidifiers.
    15. Availability of support: supplies, transportation, communication.
    16. Distribution of output produced at the recovery site.
    17. Availability of important forms and paper stock.
    18. Ability to adapt plan to lesser disasters.

Section 12. Disaster site rebuilding

Use this information to do disaster site rebuilding.
    • Floor plan of data center.
    • Determine current hardware needs and possible alternatives.
    • Data center square footage, power requirements and security requirements.
      • Square footage ____________
      • Power requirements ____________
      • Security requirements: locked area, preferably with combination lock on one door.
      • Floor-to-ceiling studding
      • Detectors for high temperature, water, smoke, fire and motion
      • Raised floor
    • Vendors
      You can attach the vendors information here.
    • Floor plan
      You can include a copy of the proposed floor plan here.

Section 13. Record of plan changes

Keep your plan current, and keep records of changes to your configuration, your applications, and your backup schedules and procedures.

  • You can get print a list of your current local hardware by typing the following command:

    DSPLCLHDW OUTPUT(*PRINT)
Filed Under: Templates Tagged With: , , , , , ,

FEMA Mitigation Assessment Group Report on Spring 2011 Tornadoes

August 2, 2012 by Leave a Comment

Posted by: Sandra Knight, Deputy Federal Insurance and Mitigation Administrator, Mitigation

A little over a year ago, hundreds of tornadoes touched down in the Southeastern and Midwestern portions of the United States between April 25 and April 28, 2011. On May 22, only a few weeks later, a powerful 0.75-mile-wide tornado cut a 6-mile path through Joplin, MO. These tornado events resulted in the tragic loss of life, destruction of thousands of homes and billions of dollars in building and infrastructure damage. FEMA’s Building Science Branch responded by deploying a Mitigation Assessment Team of specialists to assess building damage across a five-state area comprised of Alabama, Georgia, Mississippi, Tennessee, and Missouri.

Because every individual loss is a community loss, our primary goal was to assist recovery efforts by distributing timely and applicable guidance for recovery and reconstruction. We assessed the performance of the buildings and various infrastructure affected by the tornadoes, document selected safe room and storm shelter performance in the affected areas, and describe the lessons learned that could reduce future loss of life and damage to buildings and infrastructure from tornado events. A report with the results of our observations, conclusions and strategic actionable recommendations to help reduce future building damage and loss of life from tornadoes was recently published.

In the first months following the tornadoes, the MAT published eight Recovery Advisories, participated in the Safer Alabama Summit in June 2011, and held numerous public training sessions in affected areas in the summer of 2011 and spring of 2012. The report with the details of the MAT field observations, conclusions, and recommendations is now published and available to be downloaded as FEMA P-908, Mitigation Assessment Team Report – Spring 2011 Tornadoes: April 25-28 and May 22; Building Performance Observations, Recommendations, and Technical Guidance (May 2012). FEMA P-908 was released to the public on May 22, 2012, the one-year anniversary of the tornado event in Joplin.

The report was developed and reviewed by a team of over 200 design and construction experts from various industry groups, academic institutions, nonprofit associations, government agencies, and small and large businesses. FEMA P-908 presents the MAT’s observations, 47 conclusions, and 49 actionable recommendations directed at strategically improving public safety and building performance during tornado events through defining research needs, proposing national code and standard changes, and providing local governments, individuals, design professionals, building owners and key federal agencies with actions they can take. FEMA P-908 also describes in detail the historic storms and building codes in the affected areas and includes an appendix with prescriptive guidance for enhanced construction techniques to improve the performance of wood-frame residential structures when impacted by tornadoes rated EF2 or less.

The MAT’s recommendations addressed a range of building and life-safety issues. Several of the recommendations are already being implemented:

  • FEMA submitted a proposal in January 2012 to the International Code Council for the 2015 update of the International Building Code to require that a safe room or storm shelter be included when new schools and critical facilities meeting certain criteria are built; this proposal passed in the April 2012 committee hearings. 
  • A change to the risk category and addition of extensive commentary on tornado loads is being planned for submission to the American Society of Civil Engineer’s Minimum Design Loads for Buildings and Other Structures (ASCE 7). 
  • This publication combined with FEMA’s technical guidance for the construction of Individual and Community Safe Rooms, provides individual residents, community planners and emergency managers with the information necessary to get started on projects and plans that will better prepare them for next year. 
  • FEMA is planning additional outreach activities to highlight the MAT’s observations, conclusions, recommendations, and reporting efforts. 

What MAT means for the future
The MAT serves several purposes for future disasters and future mitigation activities. Future disasters with similar impacts will have the published MAT Reports and Recovery Advisories available to them immediately as an expert source of how buildings fail or resist extreme winds. As soon as the recovery starts, organizations involved in the recovery could use this existing pool of standards, best practices, and guidance to build back safer, stronger and more resilient.

The MATs work also helps FEMA continually validate the design and construction guidance it produces for the public, the success of FEMA funded Mitigation projects and the documentation needed to strengthen and update the voluntary, private sector, consensus building codes and standards in this county that the public relies on.

Visit www.fema.gov/rebuild/buildingscience for more information on the FEMA Building Science Branch.

7492243984336094433 7423164478823863563?l=blog.fema
Filed Under: FEMA Tagged With:

Free Business Continuity Plan Template

July 30, 2012 by Leave a Comment

Free Business Continuity Plan Template

Filed Under: Templates

Faith-Based Group Rebuilds Alabama Church Following 2011 Tornadoes

July 12, 2012 by Leave a Comment
Editor’s note: This was originally posted June 28, 2012, on the White House blog by David L. Myers, Director of the Department of Homeland Security Center for Faith-based & Neighborhood Partnerships.

Tornadoes and fires hold more in common than being disasters: they can also make good neighbors.

This is uniquely true in Boligee, AL, a small rural town near the Mississippi border, and Hartville, OH, near Akron. It’s a great story of faith communities helping each other — and it has a beautiful twist at the end.

The story begins in and around Boligee in 1996, when four African American churches burned to the ground. Though it has never been proven, many suspect the fires were related to racial tension. Volunteers from around the world rebuilt the four churches — including Little Zion Baptist Church — with the assistance of Quakers and Mennonites.

Fast forward to April 27, 2011, when tornadoes tore through central Alabama, killing 139 people and destroying billions of dollars of property, including the Christian Valley Baptist Church in Boligee, home of a small African American congregation.

broken down building

The Christian Valley Baptist Church in Boligee, AL, a small African American congregation, was destroyed by a tornado in April 2011. (Photo courtesy of David L. Myers)

ROPE OF HOPE

The Rev. Tracy Giles, Christian Valley’s pastor, didn’t know what to do. Insurance would cover $ 165,000, but estimates to rebuild the church exceeded $ 500,000. Pastor Giles heard about Mennonite Disaster Service and sat down over coffee with one of its coordinators, Jerry Klassen. Pastor Giles told Klassen, “I need a thread of hope.”

Klassen responded, “I can throw you a rope of hope.”

Klassen contacted Maple Grove Mennonite Church in Hartville, and soon skilled volunteers from several Hartville churches were making regular treks to Boligee. On Sunday, June 3, 2012, six months after the start of the rebuilding, Christian Valley Baptist Church commemorated its new opening; total cost was $ 160,000.

“It was God reaching across the borderline,” said Deacon Willie Cain.

The Rev. David L. Myers, a Mennonite minister and director of the DHS/FEMA Center for Faith-based & Neighborhood Partnerships, who participated in the dedication ceremony, said it was a mutual opportunity for service. “Christian Valley Baptist cannot be itself without a church to worship in, and Mennonite churches cannot be themselves without a service project.”

rebuilt church

Christian Valley Baptist Church, rebuilt. (Photo courtesy of David Myers)

And here’s the beautiful twist: one of the biggest challenges faced every year by thousands of disaster volunteers is finding housing during their time of service. That wasn’t the case for the volunteers rebuilding Happy Valley Baptist Church.

Remember Little Zion Baptist Church, which was burned and rebuilt in 1996? That same church provided housing for more than 80 volunteers who traveled more than 800 miles from Hartville to Boligee.

Disasters of all kinds can indeed make good neighbors. 

7492243984336094433 4036334962864339011?l=blog.fema
Filed Under: FEMA

Business Continuity Plan Template Example

March 30, 2012 by Leave a Comment

This Business Continuity Plan Template was designed to assist you in the development of your Business Continuity Plan Template Example.  This Business Continuity Plan Template Example was developed using the following resources. You are free to edit the Business Continuity Plan Template Example as you see fit. To guide you in your business continuity plan please look over our business continuity checklist. The template recognizes that many small introducing firms rely on parts of a clearing firm’s BCP for many of the mission critical functions of the introducing firm. The template also contains instructions, relevant rules and Web sites, and other resources that are useful for developing a BCP for a small introducing firm.

  • This is an external release of the Connecticut Business Continuity Plan Template Example.
  • For information on the plan or Business Continuity Planning at UC
  • Fortson, Judith. Disaster Planning and Recovery: A How-To-Do-It Manual for Librarians and Archivists. New York: Neal-Schuman, 1992.
  • Jones, Virginia A. and Kris E. Keyes.  Emergency Management for Records and Information Programs.  Prairie Village, KS: ARMA, 2001.

You can download this Business Continuity Plan Template Example for free using the links below:

Microsoft Word 97-2003: Click Here

Microsoft Word 2010: Click Here

Adobe PDF:  Click Here

 

Business Continuity Plan Template Example

<Company Name>

<department name>

 

 

 

 

 

 

 

 

 

Prepared by:      , <Position>

<Name>, Consultant

                            

 

 

<Date>

 

Date of Last Review:            <Date>

Storage Location:

Primary:        

Alternate:      

 

Business Continuity Plan Template Example

TABLE OF CONTENTS:

Plan Overview….. 3

Purpose: 3

Policy: 3

Scope: 3

Assumptions: 3

Description of <department name>. 4

Location.. 4

Disaster Recovery Strategy…. 4

Plan Activation Authorization: 4

Work at Home: 4

Move to Alternate Location: 4

Plan Activation Triggers: 4

Team Roles and Responsibilities. 5

Pre-disaster Activities: 6

Emergency Identification and Response: 7

Emergency Damage Assessment / Evaluation: 7

Emergency Response Assignments: 8

Alternative / Manual Processes: 9

Post-Emergency Assignments: 9

Communications & Decision-making Protocols: 9

Returning to Normal Operations:. 9

Authorization: 9

Operating Dependencies: 10

Steps to Return to Normal Operation: 10

Plan Maintenance Procedures:. 10

Plan Review and Update Process: 10

Plan Distribution Procedures: 10

Validation Requirements: 11

Recovery Plan Validation History: 11

Additional Documentation:. 12

Location of Disaster Recovery Documentation for Supporting Systems: 12

Location of Supporting Documentation: 12

Plan Update History:. 12

Plan Sign Off… 13

 

 

 

 

Plan Overview

Purpose:

This Business Continuity Plan (BCP) will be updated in response to changes in the business environment.  The <department name> will review the plan at least annually.

 

This document outlines the steps required to operate the <department name> in the event of an unanticipated interruption of normal operations. This document will articulate the triggers for when alternate business processes need to be deployed, the steps to deploy alternate business processes, the methods for verifying that business has been properly restored and ensuring data integrity, and activities for returning to “normal” business processing.

Policy:

This BCP will only be used in situations when it is determined that business impacts and /or business risk requires alternate business processes or locations.

Scope:

This BCP is applicable for the <department name> of the <Company Name>.

Assumptions:

The plan will be implemented if systems are unavailable for 48 hours

 

  • Facilities will provide temporary space for critical staff
  • UITS will provide technical assistance for temporary location
  • Telecommunications will have phone lines available in temporary location
  • Equipment can be rented or otherwise acquired as needed
  • UITS can restore files from the latest off-site backups

 

 

 


Description of <department name>

 

Location

<Company Name>

…

…, Storrs, CT  06269

 

 

Disaster Recovery Strategy

Plan Activation Authorization:

Identify the people that are authorized to activate the various contingency plans.

 

 

Primary Name & Title Contact Data Alternate Name Contact Data
 

 

Work at Home:

If there are functions that could be performed by staff working from home, describe the approach that would be used to implement the move.

 

 

Move to Alternate Location:

If there are functions that could be performed by staff working from an alternate location, describe the approach that would be used to implement the move.

 

 

Plan Activation Triggers:

Describe the criteria that would be used to identify the need to activate one of the various contingency plans.

 

Action Trigger Criteria
 
 
 

 

Team Roles and Responsibilities

Identify the people responsible for planning, documenting, coordinating, testing, implementing, and maintaining the Business Continuity Plan.  If the size of the organization requires creations of multiple specialized teams, describe the teams and identify the members of each team.

 

Title Name Contact Information

 

 

 

Pre-disaster Activities:

List the tasks that are required on an ongoing basis, to keep the plan current and viable and indicate the person assigned to complete that task.

# Task Assignment
1
2
3
4
5
6
7
8
9
10

 

 

 

Emergency Identification and Response:

List the tasks to be performed upon discovery of a possible emergency event or notification that an emergency event has occurred.

 

# Task(All completed as quickly as possible after notification of disaster.  Notification may come from Police, Fire, or Facilities Management, depending on the group that responds first or is designated as “primary” responder.  All use the same University contact list.) Assignment
1
2
3
4
5
6

 

Emergency Damage Assessment / Evaluation:

List the tasks that are required assess the damage caused by an emergency.

 

 

# Task(All completed as quickly as possible after authorization to re-enter the damaged structure.) Assignment
1
2
3

 

 

 

 

 

 

 

 

 

Emergency Response Assignments:

List the tasks to be performed in the event that a disaster situation has been declared. 

 

 

#

 Tasks

Assignment

Estimated

Completion

Time

Date/Time Completed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 

 

 

 

 

Alternative / Manual Processes:

Describe the activities or process steps for each alternative/manual process needed to perform necessary function durin an interruption to normal operations

 

 

#

Process Step

Assignment

Estimated

Completion

Time

Date/Time Completed
1
2
3
4

 

 

 

 

Post-Emergency Assignments:

List the activities to be performed after a disaster event or after a recovery exercise.  The purpose of these is to incorporate “lessons learned” into the business continuity planning process.

 

#

Post-Disaster Responsibilities

Assignment

Estimated

Completion

Time

Date/Time Completed
1
2
3
4

 

 

Communications & Decision-making Protocols:

Describe any communication rules or guidelines that will be used during an emergency.

 

Communications with news organizations will be channeled through the University’s public relations organization.

 

Returning to Normal Operations: 

Authorization:

Identify the people that are authorized to activate plans for returning to normal operations.

 

Primary Name & Title Contact Data Alternate Name Contact Data
   
 

Operating Dependencies:

Identify operational dependencies that impact the return to normal operations.  (e.g.   applications, servers, or transaction volumes that must be in place before  processing can resume)

 

 

Steps to Return to Normal Operation:

List the tasks to be performed to return to normal operations. 

 

 

# Task(The plan for the return will be developed with Building & Grounds, but will include the general steps shown.) Assignment
1
2
3
4
5
6
7
8

 

 

Plan Maintenance Procedures:

Plan Review and Update Process:

Describe the process for keeping the plan current. 

 

Plan Distribution Procedures:

Describe the process for distributing the plan and/or training people to use its content. 

 

 

Validation Requirements:

Identify frequency and type of testing (tabletop exercises, systems / telephony testing, department recovery tests, functional tests) required for this plan. 

 

 

Recovery Plan Validation History:

Record the history of review/testing/validation activities for the plan.

 

Date:               Type Test / Results:
 
 

 


Additional Documentation:

 

Location of Disaster Recovery Documentation for Supporting Systems:

Application Document Name Location
 
 

 

Location of Supporting Documentation:

Document Name Location
 
 
 
 
 

 

Plan Update History:

Date Update Session Details Revised By
 
 

 


Plan Sign Off

This document describes the anticipated activities that will be needed to resume or continue business functions in the event of disruption to normal business activities.

 

 

 

 

 

________________________________________________                        _______________ 

Director/Department Head/Dean                                                                Date

 

Filed Under: Templates
« Previous Page