(key equipment recovery or replacement processes; alternative sources; mutual aid) Supplies Not applicable (processes to replace stock and key supplies required; provision in emergency pack) Method of recovering and Once system recovery is completed establish date and time of recovered updating data data. Use manual records to update records changed since downtime. Cascade message to all users with instructions on how to update records. Request development team to check impact on processing rules e.g. where users are required to log events within specific timescales then they may be unfairly penalised by system outage. relaxation of KPIs with commissioner if necessary. Duration If likely to extend beyond two working days then consider migrating to alternate infrastructure. Note this is a recovery process that would involve changes to DNS addressing and so required time to propagate. Use as last resort only. IT Infrastructure (Local) Operations centre at Webstar Health Critical function: Responsibility: Matt Darnell Deputy: Jenny Williams Potential impact on organisation High if interrupted: Likelihood of interruption to Low organisation: Recovery timeframe: Hardware failure: One working day Catastrophic loss of network infrastructure: see Premises Connectivity loss: see Connectivity Resources required for recovery: Staff Lead: Matt Darnell (numbers, skills, knowledge, Supported by: Jenny Williams alternative sources) Data / systems Incident should be logged with the Cegedim Service Desk. Recovery will (backup and recovery depend on the cause/issue: processes, staff and equipment Infrastructure is supported by on site next working day hardware required) replacement service. Internal connectivity is dependent on the Cisco router which is configured on the network. This is supported by a same working day support agreement. Normal operations are not dependent on information assets residing on the office network. Back up of all office data is taken daily, encrypted and stored off-site Restore from back up to existing infrastructure is between one and four hours. In the case of a catastrophic loss of the office network or connectivity then the BC/DRP for Premises or Connectivity should be invoked. WH has idle server and router capacity available if outage is prolonged. Premises Not applicable (potential relocation or options)
(key equipment recovery or replacement processes; alternative sources; mutual aid) Supplies (processes to replace stock and key supplies required; provision in emergency pack) Not applicable Method of recovering and updating data Once system recovery is completed establish date and time of recovered data. Use manual records to update records changed since downtime. Cascade message to all users with instructions on how to update records. Request development team to check impact on processing rules e.g. where users are required to log events within specific timescales then they may be unfairly penalised by system outage. relaxation of KPIs with commissioner if necessary. Duration If likely to extend beyond two working days then consider migrating to alternate infrastructure. Note this is a recovery process that would involve changes to DNS addressing and so required time to propagate. Use as last resort only. Critical function: IT Infrastructure (Local) Operations centre at Webstar Health Responsibility: Deputy: Matt Darnell Jenny Williams Potential impact on organisation if interrupted: High Likelihood of interruption to organisation: Low Recovery timeframe: Hardware failure: One working day Catastrophic loss of network infrastructure: see Premises Connectivity loss: see Connectivity Resources required for recovery: Staff (numbers, skills, knowledge, alternative sources) Lead: Matt Darnell Supported by: Jenny Williams Data / systems (backup and recovery processes, staff and equipment required) Incident should be logged with the Cegedim Service Desk. Recovery will depend on the cause/issue: Infrastructure is supported by on site next working day hardware replacement service. Internal connectivity is dependent on the Cisco router which is configured on the network. This is supported by a same working day support agreement. Normal operations are not dependent on information assets residing on the office network. Back up of all office data is taken daily, encrypted and stored off-site Restore from back up to existing infrastructure is between one and four hours. In the case of a catastrophic loss of the office network or connectivity then the BC/DRP for Premises or Connectivity should be invoked. WH has idle server and router capacity available if outage is prolonged. Premises (potential relocation or options) Not applicable
Business+continuity+and+Disaster+recovery+plan.docx