Off-Site Location

---

Scope

The scope defines the boundaries of this DR plan, such as when this plan will be invoked and how this plan will be most effective. It also gives the response teams and management teams a clear, concise image of the expectations for the execution of this DR plan. An example wording of a scope follows:

The DR plan has been developed for use in the event that access to the mission-critical data has been rendered unavailable. Recovery may be achieved from total disaster to component disaster by using all or part of this plan. Component disaster describes anything that is not considered total destruction, such as server failure, hard drive failure, and so on. This plan will not cover recovery of client workstation data, which was considered nonessential at the point this DR plan was developed.

Assumptions

It is important to disclose the assumptions made during the development of this plan. This has gotten more attention since September 11, 2001. When the DR plans were developed, companies assumed that they would be able to get across town to their data; they never assumed that the roads would be completely shut down as they were in New York for a period of time. Disclosing these assumptions at the beginning of the plan will give the response teams the ability to make decisions that fall outside this plan should they find themselves in one of those situations. Here are some sample assumptions you might make at your company:

Certain assumptions have been made during the development of this plan. The following lists the assumptions:

• Recovery site of choice is ready and available at the time of the declaration.

• Paging and telecommunication systems for public access are available.

• IT staff responsible for backup and recovery are on call and available.

• Access to public/private transportation will be available.

• Hardware will be available for use at the hot site.

• Software will be available from the off-site media storage facility.

• Air travel will not be interrupted.

---