1. Disaster Recovery Quinn Gaalswyk, CISA Senior Information Systems Auditor University of Minnesota

2. Disaster Recovery Intro. Why is a disaster recovery plan important? What should a disaster recovery plan cover? What progress has the University been making with disaster recovery planning? How should disaster recovery plans be tested?

3. Importance of a DR Plan What is a DR Plan? Why do you think a DR Plan is important?

4. Business Continuity vs. DR Plans

5. Situations a DR Plan Must Address

6. Required DR Plan Situation Types: The equipment and/or data is not available (e.g., the system crashed). The data center is not available (e.g., the building burnt down). Staff can not get to the data center (e.g. a bird flu epidemic):

7. DR Plan Recovery Components Identify key staff and reports –Staff to direct and perform the recovery process, and test results. –Reports that confirm success of recovery Process for testing the success of the recovery Equipment requirement lists and where equipment is to be maintained Recovery Time Objective (RTO) Minimum Operational Requirements (MOR)

8. Backups:

9. Overview of Backup Requirements Confirm schedule of backup –Recovery Point Objective (RPO) Confirm backups are secure –Physical Security to backups –Logical Access to backups Monitoring of backups to confirm completeness

10. Disaster Recovery vs. Cost

11. Current DR Plan Statuses?

12. DR Plan Progress at UMN OIA’s Disaster Recovery team headed by Lois Stark spearheading effort Have completed several DR Plans Provides templates for units that include key DR plan components OIA - UDMS provides a centralized backup solution for many units Utilize SAN and physical tape backups –Utilize SAN, disk storage, virtual and physical tape backups

13. Quick Comparison of Completed DR Plans PTS – EGMS Plan

14. Testing of DR Plans at the UMN