Infrastructure
Disaster Recovery & Business Continuity
Backup that has been restored from, a written order of what comes back first, and a technician on site within our hours — around the clock where the plan sits under a support agreement. We plan against the failures that actually happen to businesses this size — a dead server, a ransomware event, a flood on the floor below, a building nobody can enter — and we test the restore rather than trusting the green tick.
- Scopes it runs at
- 3
- Steps in a job
- 4
- Deliverables
- 5
- Estimate
- $0
Scope
What this looks like at your scale
Almost every business has backups. Far fewer have ever restored from them, and that is the only test that counts. The failure is rarely the backup job — it is the credentials nobody could find, the restore that needed hardware nobody had, the four days it took to discover the last good copy was eleven days old, or the plan that lived on the file server that went down. Continuity is not a product you buy; it is a rehearsal you have either done or not done.
- 01
One critical machine
The server or workstation the business genuinely stops without. Backed up properly, restored once to prove it, and documented.
- 02
A small business estate
Servers, endpoints and the systems that actually carry revenue, with a written recovery order and an agreed tolerance for how much time can be lost.
- 03
Multi-site or regulated
Where the plan has to satisfy somebody else — an insurer, an auditor, a client's vendor questionnaire — and be demonstrable rather than asserted.
How it runs
In the order the work happens
The sequence matters more than the list. Most of what goes wrong on these jobs traces back to a step skipped early rather than to the work itself.
- 01
Decide what has to come back first
Not everything is equally urgent, and pretending otherwise produces a plan nobody can execute under pressure. We establish the order — what has to be running within hours, what can wait a day, what can wait a week — and how much data you can afford to lose. Those two numbers shape everything else.
- 02
Fix the backup before designing around it
Coverage checked against what actually matters, a copy that is off-site, and a copy that cannot be reached from the machine being backed up — because ransomware that encrypts the server encrypts the share it was backing up to.
- 03
Restore from it, in advance
The step that separates a real plan from a folder. We restore to spare hardware and time it, so the recovery window is measured rather than estimated, and so the missing credential is found on a Tuesday rather than during the incident.
- 04
Write it down where you can reach it
The order of recovery, the credentials, the vendor numbers, and who calls whom — held somewhere reachable when the network is down, which means not only on the network. Then we rehearse it with the people who would run it.
What you get
What is actually delivered
- Backup coverage audit against what the business actually needs
- A tested restore, timed, to real hardware
- Written recovery order with agreed time and data-loss tolerances
- Credentials and vendor contacts held off the network
- A walkthrough with the people who would have to run it
Not this
What we do not do here
Stating this is what makes the rest of the page worth believing, and it saves you a call that was never going to end in work.
- Incident response and forensics on an active compromise. If you are being extorted right now, you need a specialist response firm and we will tell you that in the first minute rather than the first hour.
- Cyber insurance underwriting and claims handling, though we will help you answer the questionnaire truthfully.
- Legal and regulatory breach notification, which is counsel's call.
Questions
Before you call
- We already have backups. Is this still worth it?
- The question is whether anyone has restored from them. A backup nobody has tested is a hypothesis. Most of the value here is in the first restore, which is also where the unwelcome surprises live — and finding them on a scheduled Tuesday is enormously cheaper than finding them during an outage.
- How quickly could we be running again?
- That is the number the plan exists to establish, and it depends on what has to come back first and what hardware is available. We measure it during the test restore rather than quoting you a figure we have not demonstrated.
- What if the whole office is inaccessible?
- That is one of the cases the plan has to cover, and it is a common one — a flood, a fire on another floor, a building closed by the city. It changes what has to be off-site and what has to be reachable without being in the building, which is why it is decided in advance.
Related
Usually bought alongside
- Field Services
Endpoint & Access Hardening
Close the gaps that an audit — or an incident — will find first.
- Engineering
Custom Software Engineering
Production applications built by the people who also run the infrastructure.
Next step
Need Disaster Recovery & Business Continuity?
Free diagnostics and a written estimate before anyone is dispatched. Tell us the site and the deadline and we will tell you what it takes.
- Free diagnostics
- Same-day across most of the metro
- Named technicians
- No fix, no labour charge