help5
bcs
help5.docx
Topic Portfolio 5 pages excluding references: create a Disaster Recovery plan on any financial organization.
Need content as in the below requested format
References requirement
NOT accept references from Journals or Books.
as well it should be in-text citations and a reference page conforming to APA only
Format:
Revision History
|
Revision |
Change |
Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Official copies of the document are available at the following locations:
1. Department of Information Technology Office
1. Office and home of the Chief Information Officer
Contents
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.0.1 Incident Commander 3 5.0.2 Incident Command Team 3 5.1 Datacenter Recovery Team 3 5.2 Desktop, Lab, and Classroom Recovery Team 4 5.3 Enterprise Systems Recovery Team 4 5.4 Infrastructure and Web Recovery Team 4 5.5 Telecommunications, Network, and Internet Services Recovery Team 4 Section 6: Recovery Preparations 5 6.1 Data Recovery Information: 5 6.2 Central Datacenter and Server Recovery Information: 5 6.3 Network and Telecommunication Recovery Information: 5 6.4 Application Recovery Information: 5 6.5 Desktop Equipment Recovery Information: 5 Section 7: Disaster Recovery Processes and Procedures 5 7.1 Emergency Response: 5 7.2 Incident Command Team: 5 7.3 Disaster Recovery Teams: 5 7.4 General System/Application Recovery Procedures/Outline: 5 8.0 Network & Telecommunication Recovery Guidelines: 7 Appendix A. IT Contact List 7 Appendix B. Crisis Management Team Contact List 7 Appendix C: IT Recovery Priority List 7 C.1 IT Infrastructure Priorities: 7 C.2 IT System Priorities: 8 C.3 Consortium, Outsourced, and Cloud-based IT System Priorities: 8 C.4 IT Facility Priorities 9 Appendix D: Vendor Information 9 Appendix E: Disaster Recovery Signoff Sheet 10
Section 1: Introduction
Provide an introduction to the company/situation...
A copy of this plan is stored in the following areas:
0. Department of Information Technology Office
0. Office and home of the Chief Information Officer
Section 2: Scope
Determine/explain the scope of this plan.
Section 3: Assumptions
Section 4: Definitions
Section 5: Teams
0. Incident Commander
|
Chief Information Officer |
|
|
Home Phone: |
|
|
Cell Phone: |
|
0. Incident Command Team
|
Chief Information Officer |
|
|
Manager, User Support |
|
|
Manager, Infrastructure Services |
|
|
Manager, Information Systems |
|
|
Manager, Classroom and Media Services |
|
0. 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) |
0. 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 |
0. 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.) |
0. 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 |
0. 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 |
Section 6: Recovery Preparations
0. Data Recovery Information:
0. Central Datacenter and Server Recovery Information:
0. Network and Telecommunication Recovery Information:
0. Application Recovery Information:
0. Desktop Equipment Recovery Information:
Section 7: Disaster Recovery Processes and Procedures
0. Emergency Response:
0. Incident Command Team:
0. Disaster Recovery Teams:
0. General System/Application Recovery Procedures/Outline:
8.0 Network & Telecommunication Recovery Guidelines:
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.
0. IT Infrastructure Priorities:
0. IT System Priorities:
0. Consortium, Outsourced, and Cloud-based IT System Priorities:
|
Application/System Name |
Priority |
RTO |
RPO |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1. Critical – Basic infrastructure and must be restored as soon as possible.
1. High – Systems of extreme importance, but do not provide infrastructure.
1. Medium – Important systems and applications, but do not have university-wide impact.
1. Low – Systems important to specific departments or specific small populations of users.
1. 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
0. IT Facility Priorities
|
Building Name |
Priority |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: building list continues on next page.
1. Critical, needed for maintenance of public health and safety, communications.
1. 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).
1. Medium, needed for mission of university, delivery of classes.
1. Low, everything else
Appendix D: Vendor Information
Appendix E: Disaster Recovery Signoff Sheet
I have been briefed and given an overview of the Disaster Recovery Plan and I am familiar with my responsibilities.
|
Name |
Signature |
Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
