You are a disaster recovery specialist working for a local university. The IT services team you lead just finished writing an updated Business Continuity and Disaster Recovery (BCDR) plan. The university has a variety of goals with stakes in research, education, and healthcare. The BCDR plan addresses the steps required to resume normal business operations, which systems and departments are mission-critical, and the responsibilities of leaders and personnel in various disaster scenarios.
The BCDR plan addresses several disaster scenarios, ranging from IT-centric DDoS attacks to physical disasters resulting in destroyed servers and disks or lost work areas. It defines recovery tasks and sub-tasks, the personnel responsible, and prioritizes the tasks by department and function. The BCDR plan includes a timeline for tasks to be accomplished. It also lists critical vendors, contact information, and specific types and quantities of resources required to achieve partial and complete recovery.
The next step is testing the procedures laid out in the BCDR plan. Your task is to plan tests for your team's BCDR plan and determine the scope and nature of the tests. You also write up a detailed fictional scenario for use in these tests. The scenario consists of multiple disruptions. In the scenario, a fire breaks out in the server room in the administrative building, compromising over 80% of the student account data. This incident occurs during a wave of influenza, and 30% of staff members are at home sick. The fire has also affected about 10% of the servers containing patient medical data in the nearby health services administration building.
Key Points in the BCDR Plan:
- At least two heads of departments to "call" a disaster
- A single "warm" site is available that can be quickly converted for use
- Maps of meeting points for employees, including routes
- Vendor contact information
- Communication plans – who is responsible for informing whom?
- Alternative process flows for failures in primary processes
- Easy-access checklists for what to do and what not to do
- Which systems to recover, in which order, and how to do so
- Non-technical responsibilities of end users
Scope of Testing:
- Non-recoverable systems or irretrievable data loss
- Missing dependencies, software errors or missing recovery-time objectives
- Lack of familiarity and comfort with disaster recovery processes on the part of employees, staff and department leaders
To return this interactive to its initial state, click Reset.