![]()
This blog post is focused on how to plan and scope out a disaster recovery plan. It looks at the objectives, work packages or deliverables and the acceptance criteria. It is more focused on how a client might engage a vendor to conduct a disaster recovery plan. The structure outlined could be used for inclusion in a statement of work. This is a business focused post and not technical.
A disaster recovery plan (DRP) is a documented process or set of procedures to recover and protect a business IT infrastructure in the event of a disaster. Planning and testing a disaster recovery plan is a prudent part of business continuity planning.
This post is part of a number of articles on projects, you can read more here.
Are you enjoying this blog? If so, please forward this to a friend or colleague and suggest that they sign up here. It is free and you will receive a coupon code to allow a free download from our store + regular updates on tools, templates and interviews to help get it done ! You may also find some of the tools and templates that I have used to deliver projects for startups here, including the most popular item in the store, a project quote tool that helps you build a fully costed project commercial model. You can find it here. All products are offered with a money back guarantee.
Objective
Disaster Recovery Plan Execution and Validation involves executing the Service or Business Continuity Plan in the event of a disaster or any other disruption where normal restore procedures cannot be used to recover the application within an acceptable period for the business. Objective of the engagement Develop and provide a Disaster Recovery Implementation Plan and Disaster Recovery Plan, execute the plan in a controlled manner, provide a report on the annual disaster recovery test conducted. Environment Scope
It is important to specify the scope of the environments to be tested whether it be production, development or test or a combination of all three. For example it may not be necessary to conduct a disaster recovery plan on the TEST environment because the business impact is so low, it could be restored from a back up in a few days with little impact to inflight projects. Disaster Recovery Services (typical)
Project Deliverables Project exclusions
Project Assumptions
Project Dependencies
Risks The criticality of the Business Process or System is determined by the Business Impact should a critical incident be experienced. This result is then tied into the Risk Disaster Recovery criteria such as:
The risk can then be included in a table and expressed in the following way.
This should give you a good basis for engaging a vendor or supplier to conduct a disaster recovery plan on your behalf. Thanks for reading Andrew Everett
0 Comments
Your comment will be posted after it is approved.
Leave a Reply. |
Categories
All
A$4.00
For the project office to use. A list of things to check off in managing a project grouped into sections from scope, time, budget, quality and management. Instantly check the health of any project by scoring against these 117 questions.
A$4.00
The following is a project checklist, which can be used by project managers, program managers, delivery managers, pre sales consultants and anyone who is focused on ensuring that all areas of a project are being managed to ensure successful delivery. It is organised around the lifecycle of a project from initiation through delivery and close out.
Archives
November 2019
|