Students will create a Disaster Recovery Plan (usingMS Office Word or equivalent) for either the organization they work for or one they wish to work for in the future. This would be best for students
INFORMATION TECHNOLOGY DISASTER RECOVERY PLAN
Your Name
XXX
XXX
XXX
Date
Revision History Revision | Change | Date |
Department of Information Technology Office
Office and home of the Chief Information Officer
Revision History 1
Official copies of the document are available at the following locations: 1
Contents 2
Section 1: Introduction 3
Section 2: Scope 3
Section 3: Assumptions 3
Section 4: Definitions 3
Section 5: Teams 3
5.1.1Incident Commander 3
5.1.2Incident Command Team 3
5.1Datacenter Recovery Team 3
5.2Desktop, Lab, and Classroom Recovery Team 4
5.3Enterprise Systems Recovery Team 4
5.4Infrastructure and Web Recovery Team 4
5.5Telecommunications, Network, and Internet Services Recovery Team 5
Section 6: Recovery Preparations 5
6.1Data Recovery Information: 5
6.2Central Datacenter and Server Recovery Information: 5
6.3Network and Telecommunication Recovery Information: 5
6.4Application Recovery Information: 5
6.5Desktop Equipment Recovery Information: 5
Section 7: Disaster Recovery Processes and Procedures 5
7.1Emergency Response: 5
7.2Incident Command Team: 5
7.3Disaster Recovery Teams: 5
7.4General System/Application Recovery Procedures/Outline: 5
8.0 Network & Telecommunication Recovery Guidelines: 5
Appendix A. IT Contact List 5
Appendix B. Crisis Management Team Contact List 6
Appendix C: IT Recovery Priority List 6
C.1IT Infrastructure Priorities: 6
C.2IT System Priorities: 7
C.3Consortium, Outsourced, and Cloud-based IT System Priorities: 7
C.4IT Facility Priorities 8
Appendix D: Vendor Information 8
Appendix E: Disaster Recovery Signoff Sheet 9
Section 1: IntroductionProvide an introduction to the company/situation...
A copy of this plan is stored in the following areas:
Department of Information Technology Office
Office and home of the Chief Information Officer
Determine/explain the scope of this plan.
Section 3: Assumptions Section 4: Definitions Section 5: Teams- Incident Commander
Chief Information Officer | |
Home Phone: | |
Cell Phone: |
- Incident Command Team
Chief Information Officer | |
Manager, User Support | |
Manager, Infrastructure Services | |
Manager, Information Systems | |
Manager, Classroom and Media Services |
- Datacenter Recovery Team
All Contact Information is located in Appendix A
Team Lead: | Manager, Infrastructure Services |
Team Members: | System Administrators (2) |
Desktop Systems Administrator | |
Network Communications Technicians (2) |
- Desktop, Lab, and Classroom Recovery Team
All Contact Information is located in Appendix A
Commander.
Team Lead: | Manager, User Services |
Team Members: | Manager, Classroom and Media Services |
Desktop Systems Administrator | |
Computing Coordinators (7) | |
Lab and Student Computing Coordinator | |
Equipment Systems Specialist |
- Enterprise Systems Recovery Team
All Contact Information is located in Appendix A
Team Lead: | Manager, Information Systems |
Team Members: | Manager, Infrastructure Services |
Programmer/Analysts (4) | |
Web Programmer/Analyst | |
System Administrator | |
Computing Coordinators supporting affected areas (business services, payroll, enrollment services, etc.) | |
Key Business Unit Personnel as needed by type of incident (payroll clerk, accountant, registrar, etc.) |
- Infrastructure and Web Recovery Team
All Contact Information is located in Appendix A
Commander.
Team Lead: | Manager, Infrastructure Services |
Team Members: | System Administrators (2) |
Desktop Systems Administrator | |
Web Programmer/Analyst |
- Telecommunications, Network, and Internet Services Recovery Team
All Contact Information is located in Appendix A
Commander.
Team Lead: | Manager, Infrastructure Services |
Team Members: | Communications Technicians (2) |
System Administrator |
- Data Recovery Information:
- Central Datacenter and Server Recovery Information:
- Network and Telecommunication Recovery Information:
- Application Recovery Information:
- Desktop Equipment Recovery Information:
Section 7: Disaster Recovery Processes and Procedures
- Emergency Response:
- Incident Command Team:
- Disaster Recovery Teams:
- General System/Application Recovery Procedures/Outline:
Appendix A. IT Contact List Appendix B. Crisis Management Team Contact List Appendix C: IT Recovery Priority List
The following priorities have been established by the department of Information Technology with consultation from the campus community.
- IT Infrastructure Priorities:
- IT System Priorities:
- Consortium, Outsourced, and Cloud-based IT System Priorities:
Application/System Name | Priority | RTO | RPO |
Critical – Basic infrastructure and must be restored as soon as possible.
High – Systems of extreme importance, but do not provide infrastructure.
Medium – Important systems and applications, but do not have university-wide impact.
Low – Systems important to specific departments or specific small populations of users.
Full –Systems that may not be restored to functional status until normal operations are reestablished.
Note: RTO is recovery time objective, RPO is recovery point objective
- IT Facility Priorities
Building Name | Priority |
Note: building list continues on next page.
Critical, needed for maintenance of public health and safety, communications.
High, needed for income maintenance for students, employees; payments to vendors; requirements for compliance or regulation; effect on cash flow; effect on production and delivery of services (housing, dining, student services).
Medium, needed for mission of university, delivery of classes.
Low, everything else
I have been briefed and given an overview of the Disaster Recovery Plan and I am familiar with my responsibilities.
Name | Signature | Date |