Fluent Essays

Portfolio Assignment:     Review  over the DR template and pick an industry such as (airlines, ecommerce,  banking, etc.).  Within that industry, pick a specific organization for  the development of the Disaster Recovery Plan such as Healthcare –  Physical Therapy Clinics - ATI.   Pick  an industry/company to focus on for this assignment.  Based upon the  given information you can find on the company and any past  issues/breaches the company has gone through, create a Disaster Recovery  plan using the template provided.   Project selection is submitted for approval.    ***Standard for all Research Assignments   Your paper should meet the following requirements:    Be approximately four to six pages in length, not including the required cover page and reference page. Follow APA7 guidelines. Your paper should include an introduction, a body with fully developed content, and a conclusion. Support  your answers with the readings from the course and at least two  scholarly journal articles to support your positions, claims, and  observations, in addition to your textbook. The UC Library is a great  place to find resources. Be  clearly and well-written, concise, and logical, using excellent grammar  and style techniques. You are being graded in part on the quality of  your writing. INFORMATION TECHNOLOGY DISASTER RECOVERY PLAN Revision History Revision Change Date Official copies of the document are available at the following locations: · Department of Information Technology Office · Office and home of the Chief Information Officer ( 10 ) 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: · Department of Information Technology Office · 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 5.0.1 Incident Commander Chief Information Officer Home Phone: Cell Phone: 5.0.2 Incident Command Team Chief Information Officer Manager, User Support Manager, Infrastructure Services Manager, Information Systems Manager, Classroom and Media Services 5.1 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) 5.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 5.3 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.) 5.4 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 5.5 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 6.1 Data Recovery Information: 6.2 Central Datacenter and Server Recovery Information: 6.3 Network and Telecommunication Recovery Information: 6.4 Application Recovery Information: 6.5 Desktop Equipment Recovery Information: Section 7: Disaster Recovery Processes and Procedures 7.1 Emergency Response: 7.2 Incident Command Team: 7.3 Disaster Recovery Teams: 7.4 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. C.1 IT Infrastructure Priorities: C.2 IT System Priorities: C.3 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. (2) High – Systems of extreme importance, but do not provide infrastructure. (3) Medium – Important systems and applications, but do not have university-wide impact. (4) Low – Systems important to specific departments or specific small populations of users. (5) 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 C.4 IT Facility Priorities Building Name Priority Note: building list continues on next page. (1) Critical, needed for maintenance of public health and safety, communications. (2) 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). (3) Medium, needed for mission of university, delivery of classes. (4) 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 RECOVERY  Is the recovery management process periodically reviewed and updated to ensure its effectiveness?  What is a mobile recovery center?  Are post-recovery reports prepared for use by appropriate levels of management (measurement)?  Can the backup power operate for the length of time necessary for implementing the recovery plan?  What is your recovery time objective (RTO) in hours?  What are the assumptions about the sudden spurt in data volumes that will hit the systems post recovery?  Who pays for business continuity and recovery and how much?  How well is the IT service continuity management recovery plan defined?  What is a recovery time objective (RTO)?  What critical operational or security controls require implementation prior to recovery?  What impact did the governance arrangements have on the recovery process?  How confident are you in the robustness of your organizations IT recovery and business continuity plans should you face a data breach, corruption, or loss?  Can the backup power run long enough to implement the recovery plan?  What practical recovery activities could one be doing?  What is the anticipated recovery / restoration time?  What measures will organization put in place to capture all costs associated with the recovery e ort?  Can a leading provider give clients complete freedom on security and recovery issues?  How often do you test your business recovery tech?  What are the key considerations for pursuing an internal versus a third-party recovery solution?  How many generations of backup files are needed to be sure there is rapid, accurate recovery? CHECKLIST 1  Do you test and audit recovery capability and requirements?  What communication devices would be needed at a recovery site?  Has your recovery budget increased or decreased and was that decision based on calculated costs of downtime (or other factors)?  What does a typical tape backup and recovery solution deliver?  Does your organization have an IT recovery plan?  What is your current IT recovery strategy?  Does your contract reflect current requirements for backup and recovery services?  Where should the recovery occur?  Is there a need for synchronized recovery of lost data, backed-up data and data from any continuing business transactions during an outage?  Which backup sites takes the longest recovery time?  What is the minimum number of staff and amount of space that would be required at a recovery site?  Have backup and recovery procedures been established and tested to ensure availability of data?  Is there any potential impact from common recovery sites?  Are you unable to meet your recovery time objective upon an application, database or server fault?  What is the minimum number of staff and space that would be required at a recovery site?  Is the recovery management process communicated to all affected areas within your organization?  What are the key considerations when developing recovery strategies?  Which best reflects ITIL guidance for how often an IT Service Continuity recovery plan should be tested?  What special forms or supplies would be needed at a recovery site?  Has your backup and recovery system been tested?  NOTES: BACKUP  Does your backup data be compressed?  Do you run the backup operation yourselves, or is it outsourced?  Do you restore a backup image from one PC to another PC?  How long will you save the backups?  Does the backup provider automatically encrypt your data?  Are the procedures for IT backup documented and approved by appropriate personnel?  How long server backups should be stored for?  Are you governed by any regulations surrounding your backups?  Are any backup tapes stored on-site?  Do image-level backups provide application consistency for virtual machines running a Windows OS?  How will you ensure the usability of backups?  Is the backup power automatically triggered?  What backup software is installed?  Does your organization need a data backup performance indicator?  Does your organization provide any information regarding backup/snapshot frequency needs and retention schedules?  What types of backup do you currently perform?  What viable data backup options are generally available?  How sure are you that your backups are running correctly?  How often are backups performed?  Where do you store your backup data?  What else should people consider before choosing the cloud as a backup target?  Does your organization use a data backup process? CHECKLIST 1  Does the backup studio facility have backup power?  How to choose ideal backup solution?  Do you have the most recent backup?  Which policies is related to the backup of data?  What are your perceptions of the current needs addressing backup?  What types of backup files must be routinely created?  Which backup facilities is most expensive?  What kind of backup software are you using?  How long are the daily backups kept offsite?  How will you verify automated backups ?  Are backup power sources periodically tested?  Are backups for major IT facilities performed regularly?  Is there backup power at the uplink?  When will you perform backups, while users are working, or when the system is offline?  Are backups the right solution for you?  Has management ensured that critical systems are connected to a backup power source?  Are the backup transmission feeds tested periodically?  Why is it a good idea to opt for cloud backup solutions?  Who can access onsite backup storage location?  What is the disk backup retention requirement?  What kind of systems are you using for backup?  What will be the effect of having no more periodic full backups?  How long does information live on backup in the cloud?  Are you using NAS technology with instant point-in-time backups?  How fast must data be restored from backup to prevent unacceptable downtime?  Who can access offsite backup storage location?  How often should you create backups?  How long are the weekly backups kept offsite?  Why trust your remote backups to you?  Will you perform the backups manually or schedule them to be performed automatically?  Which are possible preventive measures for backup procedures?  What are the backup specifications currently implemented?  Are you storing your backup data offsite?  Where will you store the backups to allow access by the appropriate people?  How often are your backups running?  What is your organization currently using for backup/storage policies?  Is backup data available in a way to allow multiple restores in parallel?  How satisfied are you with your backup system quality?  Do you add more PCs to your backup network after an upgrade?  How often should you perform backups?  Do you create an image backup of your entire PC?  Does the studio facility have backup power?  How does data compression affect the size of your backup data?  Are the backup power systems routinely tested?  NOTES: