The Weekly Fire Alarm Test: Why Every UK Workplace Drills for Fire but Not for IT Failure

  • 2 weeks ago
  • 0

Most workplaces accept routine fire-safety checks as part of running a business. Someone tests the alarm, records the result and follows up if it fails. Staff practise what to do in an emergency because an evacuation plan is only useful if people can act on it.

IT recovery deserves the same unremarkable discipline. A backup report that says “successful” is not proof that the business can recover. A disaster recovery plan no one has rehearsed is closer to an evacuation map nobody has read: reassuring on paper, uncertain in practice.

For an SME, an IT outage can begin with a cyber incident, accidental deletion, hardware failure or a problem with a supplier. The source may differ; the business question is the same: can essential work resume, and how soon?

A plan is not a rehearsal

Fire-alarm testing and evacuation arrangements sit within a framework of workplace fire-safety duties. Weekly alarm testing is a widely used benchmark for commercial systems under relevant British Standard guidance; the responsible person should follow the fire-risk assessment, system instructions and competent advice. Businesses also commonly practise evacuation, but the exact arrangements should reflect their premises and risk.

IT recovery is less likely to happen by default. There is no universal rule that tells every SME to test each system at the same interval. That makes it easy to defer: the backup ran, the supplier manages it, and a full exercise sounds like a large project.

The National Cyber Security Centre’s guidance for small businesses recommends regular backups, testing that information can be restored, documenting incident plans and exercising preparedness. In other words: do not assume. Check.

A backup job can complete without proving that the right data is protected, that it is usable, or that anyone knows how to restore it. A restore test provides evidence. It also exposes practical snags while the business is still operating normally: missing credentials, unclear ownership, a dependency no one recorded or an application that needs more than its data files to function.

A simple, isolated backup restore setup with a single gold status light

Make recovery as routine as the alarm test

A major disaster-recovery exercise can be valuable, but it is also easy to postpone if it demands a day of staff time, several suppliers and a complicated scenario. A small recurring test is easier to schedule and more likely to happen.

For example, an SME could:

  • restore one file to a safe test location and confirm it opens;
  • check that a priority system can be recovered in a test environment;
  • walk through one month-end recovery step, such as locating the correct data and identifying who authorises a restart;
  • ask a business user to confirm the restored information is complete and usable.

The IASME Cyber Essentials Knowledge Hub’s backup guidance recommends testing backups at least monthly. It also makes an important distinction: backups are not a mandatory Cyber Essentials technical control, but they are strongly recommended. The frequency and depth of checks should still be proportionate to the business and the systems it relies on.

Keep a short dated test log: what was tested, when, who took part, whether the restore worked, how long it took, any data gaps, and what needs fixing. A failed test is not a reason to hide the log; it is a reason to resolve the problem and test again.

Set recovery targets in business language

Two useful measures are the recovery time objective (RTO) and recovery point objective (RPO). They are most useful when agreed with the people who own the business process, not chosen as technical targets in isolation.

  • RTO: how long the business can tolerate a service being unavailable.
  • RPO: how much recent information the business can afford to lose, expressed as a period of time.

A finance director might decide that payroll must be available within a working day, while a less time-critical archive can wait longer. The acceptable loss of recent data may also differ between those services. These are examples, not recommended targets: each organisation needs to assess the consequences of interruption for itself.

Then test the targets. Record how long recovery actually took and how current the restored data was. If the result misses the agreed target, that gives management a specific decision to make: adjust the recovery arrangements, change the target, or accept and document the risk. “We have backups” is not a decision.

Make the core finance system easier to rehearse

An ageing on-premise finance or ERP system can make recovery dependent on a particular server, specialist knowledge, old documentation or a supplier whose role is unclear. A runbook that has never been walked through may omit the very steps that matter: access to credentials, system dependencies, data validation and who approves the return to service.

For suitable businesses, Microsoft Dynamics 365 Business Central can provide a supported, documented, cloud-hosted core for finance and ERP processes. That can reduce the amount of on-site infrastructure a business must rebuild, but it does not remove the need to understand data protection, user access, integrations, recovery responsibilities and business continuity.

A Dynamics 365 Jump Start can help establish whether Business Central fits the organisation’s processes and what would need to change. The recovery conversation belongs in that planning: what finance needs to keep working, what would be tested, and how users would verify that the restored service is fit for month-end work.

A dark laptop beside a ledger and clock, suggesting a rehearsed finance recovery process

Get critical knowledge out of one person’s head

Legacy systems can be reliable and deeply embedded in how a business operates. But when recovery depends on one person knowing the configuration, contacts or sequence of steps, that creates a continuity risk.

For businesses running IBM i (AS/400) systems, managed specialist cover can help replace individual memory with documented runbooks, clear ownership and 24/7 monitoring. The analogy is not that the system is a fire panel; it is that no critical recovery process should rely on one caretaker being available to explain it.

A useful runbook should be accessible to the people who may need it during an incident and should be tested with them. Managed IT Services and Helpdesk Support can provide bolt-on operational execution, but they work best when a consultant has first established the business priorities, recovery targets and responsibilities.

A technical runbook on a table in front of softly lit server equipment

Fund resilience by finding avoidable spend

Resilience is not only a technical design question. It is also a budget decision. Technology Expense Management (TEM) can review software licences, connectivity costs and overlapping suppliers to identify spending that no longer supports business needs. Where savings are found, some can be directed towards restore testing, monitoring and keeping recovery documentation current.

The principle is straightforward: fund a small amount of routine preparation rather than leave resilience unfunded until an incident forces a larger, more urgent response. An audit of Cloud Solutions, Network Solutions and Voice and Connectivity can also help identify dependencies that should appear in recovery plans.

This is where a consultancy-first approach matters. The Fractal IT Director perspective starts with business impact, ownership and recovery priorities. Specialist partners, managed services and helpdesk teams then provide the bolt-on delivery needed to put that strategy into practice.

Treat assurance as evidence, not paperwork

For organisations working towards ISO 27001, backup arrangements and ICT readiness for business continuity are relevant areas of control. Assessors will expect an organisation to demonstrate that its arrangements are defined and operating, not simply that a supplier says backups exist. Cyber Essentials is different: backup is a recommendation rather than a mandatory technical control, but reliable recovery remains important to business resilience.

A dated restore log, a documented incident exercise, agreed recovery targets and a record of corrective actions give management and assessors something concrete to review. A consultancy can guide the assessment and help align the evidence with the organisation’s real risks; it should not be mistaken for a certificate or a substitute for the organisation’s own responsibilities.

The practical goal is not a dramatic annual production. It is a recovery routine that still works when the people, systems or suppliers involved are under pressure. Start with one service, one restore and one dated entry. Put the next test in the diary. Then repeat it.

For a wider view of the Evestaff group’s services, visit evestaff.co.uk.

SEO tags: Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, IT disaster recovery testing, SME business continuity, backup restore testing, RTO and RPO, ISO 27001 consultancy, Cyber Essentials guidance

Join The Discussion