Skip to main content

ITPOL07 IT Disaster Recovery Policy V6

Page 1

ITPOL07

IT Disaster Recovery Policy

Page 1 of 13


Version:

V6

Ratified by:

Finance & Risk Committee

Date ratified:

06/05/2026

Job Title of author:

Head of Infrastructure and Cyber Security

Reviewed by Committee or Expert Group

Technology Programme Group

Equality Impact Assessed by:

Head of Infrastructure and Cyber Security

Related procedural documents

ITSOP002 Technology Disaster Recovery Plan

Review date:

06/05/2029

It is the responsibility of users to ensure that you are using the most up to date document template – i.e. obtained via the intranet. In developing/reviewing this policy Provide Community has had regard to the principles of the NHS Constitution.

Page 2 of 13


Version Control Sheet Version Final v2

Date 11/01/2015

Author Head of IT & Data

Status Awaiting approval TPB Approved TPB Updated

Final v2.1

15/01/2015

Head of IT & Data

3.0

17/01/2017

Head of IT & Data

3.1

20/06/2017

Head of IT & Data

4.0

02/01/2020

Assistant Director – IT & Systems

5.0

01/07/2023

6.0

06/05/2026

Acting Assistant Director of IT, Systems & Development Head of Infrastructure and Cyber Security

Comment Adjusted to include comments from by MP and AC by

Updated following a Major Incident Approved by TPB on 14/01/2020 Approved by FIC 05/09/23 For review

Page 3 of 13

Approved by TPB

Minor updates Minor updates changes.

and

personnel

Reviewed with minor amendments. Added definitions, strengthened DR response, preventative measures, testing and monitoring arrangements, completed the Equality Impact Assessment, and aligned to the current group-wide policy template. No material change to policy intent.


Contents 1.

Introduction .................................................................................................... 5

2.

Purpose ......................................................................................................... 5

3.

Definitions ...................................................................................................... 5

4.

Duties ............................................................................................................ 6

5.

Disaster Recovery Invocation and Response ................................................. 7

6.

Preventative Measures .................................................................................. 8

7.

Testing........................................................................................................... 8

8.

Consultation and Communication .................................................................. 8

9.

Monitoring ...................................................................................................... 9

EQUALITY IMPACT ASSESSMENT TEMPLATE ................................................ 10 Stage 1: ‘Screening’............................................................................................. 10 EQUALITY IMPACT ASSESSMENT TEMPLATE ................................................ 12 Stage 2 ................................................................................................................ 12

Page 4 of 13


1. Introduction Provide services are increasingly reliant on its technology systems and this reliance will continue to grow as services increase their use of systems and data. This policy is in place to ensure all reasonable steps are taken to ensure that in the event of IT Service Disruption, we will be able to restore the IT services as soon as possible in the circumstances prevailing at the time.

2. Purpose This policy sets out principles, guidance and requirements with the aim of ensuring that: • • • • • •

Critical technology systems can be restored in an efficient manner following any major failure, adverse event, disaster or loss of technology systems. Appropriate business continuity and disaster recovery plans are in place. Critical technology systems are identified. Risks to technology systems are continually being reviewed and avoided or reduced. Full documentation, including test plans, are in place. All major failures, adverse events and incidents are fully investigated and lessons learnt.

3. Definitions Disaster Recovery The process of restoring technology systems, infrastructure, applications and data following a major failure, adverse event, disaster or loss of technology systems. Disaster Recovery Plan The documented plan that sets out how critical technology systems will be restored following a disaster or significant service disruption. Business Continuity Plan A service-level plan that sets out how a service will continue to operate during disruption, including where technology systems are unavailable. Critical Technology System A technology system, application, infrastructure component or data service that is essential to the delivery of Provide services and requires prioritised recovery. IT Service Disruption An interruption, degradation or loss of availability of one or more technology systems, applications, infrastructure components or data services. Technology Major Incident A significant technology incident that causes, or has the potential to cause, major disruption to critical services, systems or data.

Page 5 of 13


Technology Major Incident Team (TMIT) The group responsible for assessing significant technology incidents and agreeing whether the Disaster Recovery Plan should be invoked. Recovery Time Objective (RTO) The target time within which a system, application or service should be restored following a disruption. Recovery Point Objective (RPO) The maximum acceptable amount of data loss, measured as the period between the last recoverable backup or recovery point and the disruption. Backup A copy of data, systems or configuration information retained so that it can be restored following data loss, corruption, system failure or disaster. Resilience The ability of technology systems, infrastructure and processes to withstand disruption and continue operating or recover effectively.

4. Duties To enable the successful management of Disaster Recovery plans and procedures, all staff should be aware of their roles and responsibilities:

Executive Directors •

Responsible for ensuring procedures are in place within their directorates that ensure staff are aware of their responsibilities contained within this policy and that these responsibilities are adhered to.

Director of IT • • • •

Ensuring there are appropriate plans in place to restore technology systems in the event of a disaster. Ensuring all critical applications and hardware have support contracts in place. Ensuring that technology systems are designed for resilience. Ensuring that up-to-date documentation exists for all key technology processes.

Head of Infrastructure and Cyber Security • •

Ensuring computer systems including applications and servers are appropriately backed up. Ensuring that there are UPS units connected to all critical equipment in case of power failure.

Service Managers • • •

Responsible for ensuring they have their own Business Continuity Plan in place should technology systems be unavailable. Ensuring data for their service is saved in appropriate locations where it will be backed up and not on local devices. Ensuring that all incidents relating to data security are reported using DATIX. Page 6 of 13


• •

Ensuring their staff have read and understood this policy. Ensuring a hard copy of names and contact details for their team is kept.

All Staff • • • • •

Must ensure all desktops, laptops and tablets issued to them are regularly connected to the Provide network. Responsible for contacting the Technology Service Desk to report problems and any damage caused or discovered to IT equipment contemporaneously. Ensure that their data is saved in appropriate locations where it will be backed up and not on local devices. Ensuring IT equipment is used in an appropriate manner and only for work purposes. Comply with the terms of the Information Security Policy.

Technology Team • • •

Ensuring own familiarity with DR procedures and plans. Ensuring planned tests are carried out and results documented. Ensuring changes to hardware and software are documented.

5. Disaster Recovery Invocation and Response The Provide Technology Team will maintain a Disaster Recovery Plan to ensure that all critical technology systems are identified and can be restored in an efficient manner with the least disruption to essential services in the event of a disaster. Critical technology systems should have agreed recovery priorities, Recovery Time Objectives and Recovery Point Objectives documented within the Disaster Recovery Plan. The Disaster Recovery Plan can be invoked following agreement by the majority of the Technology Major Incident Team (TMIT) which can be convened by any member of the TMIT, examples of when this may occur are: 1. 2. 3. 4. 5. 6. 7.

Critical data corruption Deliberate external or internal attacks Theft of essential network equipment Essential component failure Major power outage Physical damage to essential hardware Loss of access to essential equipment

Disaster Recovery (DR) should only be invoked if a prolonged outage to a system or systems is envisaged following an incident. This may follow a period of operation under the Business Continuity Plan. For example; a failure of a critical component that is under contract to be replaced within 4 working hours should not necessitate the DR being invoked. If the component is not available and likely to take 2 days to be replaced then DR may be invoked. Members of the TMIT must be familiar with Provide’s Major Incident Plan. The loss of critical IT systems may lead to the organisation declaring a Major Incident, and a nontechnology Major Incident, such as a large fire, could cause a Technology Major Incident. Page 7 of 13


Where a disaster recovery event is related to a cyber security incident, recovery activity must be coordinated with relevant cyber incident response, information governance and communications processes.

6. Preventative Measures Regular risk assessments should be undertaken by the Provide Technology Team to identify risks and actions to be taken to significantly reduce or avoid the risks that could lead to a disaster, these should include: • • • • • • • • •

Automated Fire Suppression fitted to major server rooms Electronic access control systems fitted to all server rooms Environmental monitoring systems fitted to all server rooms Dual Interlinked air conditioning units fitted to all major server rooms Uninterruptible Power Supplies (UPS) fitted within all server rooms UPS connected to all critical IT equipment Regular inspection of critical equipment Disaggregated systems to be used where feasible Backups for critical systems should be appropriately protected from accidental deletion, unauthorised access and cyber attack

7. Testing Where the Disaster Recovery Plan has not been used and reviewed in the previous year, the Provide Technology Team will undertake a yearly disaster recovery test to: • • • • • • •

Ensure recovery times are minimised. Validate the recovery process, ensuring smooth restoration in the event of a real disaster. Test resources required during a recovery such as power supplies. Confirm current systems will support a full and effective recovery. Ensure staff are familiar with their roles and responsibilities. Ensure documentation of this procedure is kept up to date. Ensure the process of returning to normal operational state after DR is effective and fully understood.

8. Consultation and Communication This policy has been reviewed by the Technology Programme Group and relevant subject matter experts. Once ratified, the policy will be published and communicated to relevant managers and staff. Line managers are responsible for ensuring staff are aware of their responsibilities under this policy.

Page 8 of 13


9. Monitoring The effectiveness of this policy will be monitored through planned Disaster Recovery testing, review of recovery activity following any real-life event, and ongoing oversight of key disaster recovery controls. The policy will be reviewed every three years, or sooner following a significant technology change, Disaster Recovery test, real-life event or identified lesson learned. Following any DR test or real-life event, lessons learned should be documented and tracked to completion. What is monitored Disaster Recovery Plan review DR test completion

By whom

Frequency

Evidence

Head of Infrastructure and Cyber Security Infrastructure Team

Updated DR Plan

Actions from DR tests or real events Critical system backup status Critical system support arrangements

Head of Infrastructure and Cyber Security Infrastructure Team Director of IT / Head of Infrastructure and Cyber Security

Annually or following major change Annually unless used/reviewed during a real event After each test/event Regularly

Backup monitoring/reporting Support contract records

At least annually

Page 9 of 13

DR test report Lessons learned/action log


EQUALITY IMPACT ASSESSMENT TEMPLATE Stage 1: ‘Screening’ The Equality Impact Assessment needs to be completed so that any decisions made are compliant with the aims of the Public Sector Equality Duty – and that any adverse impact for any protected characteristics are identified and resolved. Policy Title

IT Disaster Recovery Policy Provide a brief summary (bullet points) of the aims of the Policy

This policy sets out the principles, responsibilities and requirements for restoring critical technology systems following a major failure, adverse event, disaster or loss of technology systems. EQIA Assessor Name and Job Title

Date of Assessment

Bradley Hampson, Head of Infrastructure and Cyber Security

06/05/2026

This stage establishes whether a proposed initiative will have an impact from an equality perspective on any particular group of people or community or whether it is “equality neutral” (i.e. have no effect either positive or negative)

Q1. Will this policy affect one of the following groups more or Less favourably than another?

Group

More

Less

Neutral

Details If more or less, explain impact and any valid legal and/or justifiable exception. Include the source of any evidence

Age Consider impact and detail across age ranges on old and younger people. This can include safeguarding, consent and child welfare Disability Consider and detail impact on attitudinal, physical, and social barriers. Sex Consider and detail impact on men and women (potential to link to carers) Gender reassignment (including transgender) Consider and detail impact on transgender and transsexual people. This can include issues such as privacy of data and harassment. Pregnancy and maternity Consider and detail impact on working arrangements, part-time working, infant caring responsibilities.

x

x x x

x

Page 10 of 13


Race Consider and detail impact on different ethnic groups, nationalities, Roma gypsies, Irish travellers, language and communication barriers. Religion or belief Consider and detail impact on people with different religions, beliefs or no belief. Sexual orientation Consider and detail impact on heterosexual people as well as lesbian, gay and bi-sexual people Carers Consider and detail impact on part-time working, shift-patterns, general caring responsibilities Other identified groups Consider and detail on different socioeconomic groups, area inequality, income, resident status (migrants) and other groups experiencing disadvantage and barriers to access.

Assessed Impact overall

Neutral

x

x

x

x

x

Is the impact of the initiative – whether positive or negative significant enough to warrant a more detailed Stage 2 assessment?

X No

Guidelines: Things to consider Equality impact assessments at Provide take account of relevant equality legislation and include age, (i.e. young and old,); race and ethnicity, gender, disability, religion and faith, and sexual orientation. The initiative may have a positive, negative or neutral impact, i.e. have no particular effect on the group/community. Where a negative (i.e. adverse) impact is identified, it may be appropriate to make a more detailed EIA (see Stage 2), or, as important, take early action to redress this – e.g. by abandoning or modifying the initiative. NB: If the initiative contravenes equality legislation, it must be abandoned or modified. Where an initiative has a positive impact on groups/community relations, the EIA should make this explicit, to enable the outcomes to be monitored over its lifespan. Where there is a positive impact on particular groups does this mean there could be an adverse impact on others, and if so can this be justified? - e.g. are there other existing or planned initiatives which redress this? It may not be possible to provide detailed answers to some of these questions at the start of the initiative. The EIA may identify a lack of relevant data, and that data-gathering is a specific action required to inform the initiative as it develops, and also to form part of a continuing evaluation and review process. It is envisaged that it will be relatively rare for full impact assessments to be carried out at Provide. Usually, where there are particular problems identified in the screening stage, it is envisaged that the approach will be amended at this stage, and/or setting up a monitoring/evaluation system to review a policy’s impact over time. Page 11 of 13


EQUALITY IMPACT ASSESSMENT TEMPLATE Stage 2 To be used where the ‘screening phase has identified a substantial problem/concern) This stage examines the initiative in more detail in order to obtain further information where required about its potential adverse or positive impact from an equality perspective. It will help inform whether any action needs to be taken and may form part of a continuing assessment framework as the initiative develops. Policy/ Project Title

EIA Assessor Name and Job Title

Date of Assessment

EIA Review by Chief Officer name and Job Title

Date Of Review

Outcome of Chief Officer Review Q1. What data/information is there on the target beneficiary groups/communities?

Are any of these groups under- or over-represented? Do they have access to the same resources?

   

Yes No Yes No

 

Yes No

What are your sources of data and are there any gaps?

Q2. Is there a potential for this initiative to have a positive impact, such as tackling discrimination, promoting equality of opportunity and good community relations? If yes, how? Which are the main groups it will have an impact on?

Q3. Will the initiative have an adverse impact on any particular  Yes group or community/community relations?  No If yes, in what way? Will the impact be different for different groups – e.g. men and women?

Q4. Has there been consultation/is consultation planned with  Yes stakeholders/ beneficiaries/ staff who will be affected by the  No initiative? Summarise (bullet points) any important issues arising from the consultation

Page 12 of 13


Q5. Given your answers to the previous questions, how will your plans be revised to reduce/eliminate negative impact or enhance positive impact?

Are there specific factors which need to be taken into account?

 

Yes No

Q6. How will the initiative continue to be monitored and evaluated, including its impact on particular groups/ improving community relations? Where appropriate, identify any additional data that will be required

Guidelines: Things to consider An initiative may have a positive impact on some sectors of the community but leave others excluded or feeling they are excluded. Consideration should be given to how this can be tackled or minimised. It is important to ensure that relevant groups/communities are identified who should be consulted. This may require taking positive action to engage with those groups who are traditionally less likely to respond to consultations, and could form a specific part of the initiative. The consultation process should form a meaningful part of the initiative as it develops, and help inform any future action. If the EIA shows an adverse impact, is this because it contravenes any equality legislation? If so, the initiative must be modified or abandoned. There may be another way to meet the objective(s) of the initiative.

Page 13 of 13


Turn static files into dynamic content formats.

Create a flipbook