Overview
Background
Previously up to 2016, there was no consistent Disaster Recovery review and testing performed for over 10 years.
Significant technical debt in the Disaster Recovery was built up, leaving University priority services at risk in case of major Disasters.
This project has two main objectives:
-
Build upon the 2016 Disaster Recovery project (INF120), by picking up recommendations:
- Review Disaster Recovery documentation location.
- Improve documentation related to Disaster Recovery for Top and medium priority services.
- Review and update the Disaster Recovery documentation produced in the 2016 initial Disaster Recovery project.
Scope
This project’s focus is to review the University’s priority services managed by IS Applications, this is to include Top and Medium Priority Services. Please note where any of these services are managed by 3rd party supplier (e.g. Cloud based) we will document components that are shared and collaborate with the owning infrastructure area, such IT Infrastructure, to link to their documented Disaster Recovery Plans.
Out of scope: Project budget is set at 15 days max, therefore this project cannot complete any DR tests (including Top or Medium priority services). Please note that there are other services which are not classed as top or medium priority - reviewing the documentation for these services is out of scope on this project.
Objectives, Deliverables, Success Criteria, Benefits, and Priority
Objective |
Deliverables |
Success Criteria |
Benefits |
Priority |
1. To establish the set of components which are used by the priority services Applications |
Review all applications and components which make up the Top and Medium priority services
|
|
1. Agreement on the list of Top and Medium priority services produces clarity and means that resources can be focussed where needed most, reducing overall support costs in ISG. |
1.1 Review all applications and components comprising the top and medium priority services (Must Have) |
2. To review and update a Disaster Recovery plan, where required, for each of the applications noted as top and medium priority services |
(Review DR Dashboard) Establish a DR position for each application: For each Top and Medium priority service have a DR document/plan - there must be a written document on how to recover that application. This may link to existing documentation.
|
|
2. This project will identify any potential gaps in project and /or support documentation and inform possible changes to process for completion of technical documentation.
3. Reduce any reputational risk to IS Applications to support Top and Medium Priority Services in the event of a Disaster recovery situation |
2.1 Establish a DR position for each top priority application, where required (Must Have) 2.2 Establish a DR position for each medium priority application, where required (Must Have) 2.3 For each Top and Medium priority service, if none already available, produce a DR document/plan. This must include a written document, if none already available, on how to recover each application. This may link to other documents (Must Have) |
3. Review Disaster Recovery plans in established central repository and communicate any changes to appropriate support teams
|
(Review DR Sharepoint Site) Review master DR documentation |
|
4. All key technical resource within IS Applications and IT Infrastructure have a central information source with up to date application and component relating to Disaster Recovery |
3.1 Review storage and access to Master Documentation containing DR position for each component and detailing each Top and Medium priority Service DR Document / Plan (Should Have) |
Project Milestones
Stage | Milestone | Due Date |
---|---|---|
Plan | End of Planning | 29-Mar-2019 |
Deliver | Agree List of Top and Medium Priority services | 19-Apr-2019 |
Deliver | Delivery - DR documentation complete | 14-Jun-2019 |
Close | Project Closure | 28-Jun-2019 |