The Storm Season Test: Is Your IT Estate Ready for Winter Weather You Cannot Schedule?

  • 2 weeks ago
  • 0

For many UK businesses, disaster recovery means restoring a server after a technical failure. Winter weather asks a broader question: what happens when the server is fine, but the office has no power, the broadband is down and nobody can safely get in?

Storms, flooding, localised power cuts and network outages can affect whole streets or regions at once. They test the assumptions behind business continuity: how long can you operate without the office, without fixed-line connectivity, or without electricity? If the answers live only in someone’s head, they are not yet a recovery plan.

For business owners and finance directors, the start of winter is a practical moment to test those assumptions. The aim is not to eliminate every risk. It is to understand the cost of disruption, agree what matters most and invest in resilience where it will make a measurable difference.

Disaster recovery must work without the building

A backup is valuable only if it is accessible and can be restored when you need it. If copies, credentials or recovery equipment are all tied to the premises, a local flood or prolonged power cut may make them unavailable at the very moment they are needed.

Start with a site-level scenario: assume the office is closed and unavailable for several working days. Can authorised staff reach essential information from another location? Are backups held off-site or otherwise separately accessible? Has anyone tested a restore, rather than simply checked that a backup job reported success?

The UK National Cyber Security Centre advises organisations to identify critical information and systems, keep regular backups, test that information can be restored and document incident responsibilities. Its small business incident preparation guidance is a useful starting point for building a plan that can be used when normal systems are disrupted.

Agree recovery targets in business language, too. A Recovery Time Objective (RTO) is how long a service can be unavailable before the impact becomes unacceptable. A Recovery Point Objective (RPO) describes how much recent data the business can afford to lose. “Finance needs to be working by the next morning” is more useful to a leadership team than an unexplained technical target.

Then test the inconvenient version: power stays off longer than laptop batteries last, or the outage runs beyond the working day. Which tasks can staff continue remotely? Which need a manual workaround? Who informs customers, suppliers and staff, and how do they do that if the usual phone and internet services are unavailable?

A compact UPS and network equipment beside a rain-streaked office window

Voice and Connectivity are part of the recovery plan

Fixed-line telephony and broadband can be among the first services affected by a storm. A plan that assumes employees can work from home is incomplete if their home connection is also disrupted, or if the office is open but the broadband line is not.

Check what actually happens if your main connection fails. Is there a mobile fallback, such as 4G failover, and has it been tested? Can key staff use mobile data without exhausting an allowance? If you use VoIP, can calls follow the user to another device or location? Does the alternative route rely on the same network, power supply or provider as the primary one?

This is where Voice and Connectivity planning meets Network Solutions: the question is not simply whether you have a second connection, but whether it is independent, available and usable under pressure. Include connectivity assumptions in your Disaster Recovery plan and test them before bad weather arrives.

Write down a simple communications sequence. Identify who contacts staff, suppliers and customers; which alternative channels they will use; and how frequently updates will be given. Keep essential contact details available outside the systems that may be affected.

Keep core finance moving from wherever staff can work

Month-end does not wait for the roads to clear. For businesses reliant on finance and ERP systems, the location and hosting model of the core platform can make a significant difference to continuity.

A cloud-hosted, vendor-run Microsoft Dynamics 365 Business Central environment can allow authorised staff to access finance and operational workflows from another suitable location, subject to connectivity, configuration and access controls. That is different from an ageing on-premise server in an office with no power: the server may be undamaged, but still unreachable.

A Dynamics 365 Jump Start engagement can help assess the business case, readiness, risks and practical steps involved in moving towards Business Central. It should begin with consultancy: understanding processes, dependencies, data and controls before deciding what to change. Cloud Solutions can improve flexibility, but cloud hosting is not a substitute for tested recovery arrangements, secure access or a dependable internet connection.

The right question is not “Is cloud always better?” It is “Which operating model lets us maintain the services the business depends on, at a cost and risk level we accept?”

Give legacy infrastructure a specific plan

Some organisations still depend on IBM i (AS/400) applications for important operational or financial processes. These platforms can be robust, but an on-premise installation may rely on local power, cooling, UPS equipment and specialist knowledge. A storm-related site outage can expose all those dependencies at once.

The recovery plan should cover the full estate: hardware, power protection, environmental controls, connectivity, backups, restoration steps and the people who know how to carry them out. Reducing key-person dependency matters as much as protecting the equipment. If only one individual understands the recovery process, availability depends on that person being reachable and able to help.

Specialist IBM i Management can provide managed cover and technical oversight for these environments. The strategic task is to establish what the business needs to recover, how quickly, and what support arrangements are required. Managed IT Services, Helpdesk Support and other operational services should then support that strategy, not replace it.

A carefully maintained legacy server cabinet in a dim, quiet data room

Find resilience funding in the technology budget

Before approving new failover services or equipment, check what the business already pays for. Technology Expense Management (TEM) can reveal dormant backup lines, mobile data allowances that are never used, overlapping connectivity contracts or services that do not match current working patterns.

That review can help redirect spend towards resilience that is understood and tested. A redundant connection is not useful simply because it appears on an invoice. Confirm its purpose, independence from the primary service, ownership, ongoing cost and last successful test. Likewise, a UPS needs an appropriate capacity, maintenance and a clear role; it cannot keep an office running indefinitely.

A sensible prioritisation exercise compares the cost of controls with the operational and financial impact of downtime. Protect the processes whose interruption would cause the greatest harm first, then build from there.

Make continuity evidence part of good governance

ISO 27001 and Cyber Essentials are guided consultancy domains, not badges that make an organisation immune to disruption. Weather resilience is relevant to wider security and continuity planning: physical and environmental risks, documented arrangements, clear responsibilities, and evidence that monitoring and incident response continue when normal operations are interrupted.

For flooding, the Environment Agency’s business flood plan checklist recommends setting trigger points, recording actions, identifying evacuation routes and utility shut-offs, protecting data and assigning responsibility for the response. Businesses should also check relevant local guidance, as the linked GOV.UK checklist applies to England.

Keep the plan accessible if the office is inaccessible. Include out-of-hours contacts, supplier and utility details, staff welfare arrangements, decision-making authority and a safe way to communicate. Rehearse a scenario, record what fails and update the plan. A short tabletop exercise can expose more gaps than a thick document nobody has opened since it was approved.

Ask three questions before the next storm

  1. How long can we operate without the office, electricity or our main broadband connection?
  2. What must be restored first, and what level of data loss or downtime is acceptable for each critical service?
  3. Have we tested the backup, communications and workarounds that our plan depends on?

A Fractal IT Director approach starts with those business questions, then translates the answers into proportionate technical choices. Specialist partners can provide the execution where needed; the strategy should remain joined up, cost-aware and owned by the business.

Winter weather cannot be scheduled. The response can be.

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

Join The Discussion