Home/ Services/ Disaster Recovery
SERVICE · DRAAS

When it all
goes wrong.
We've got you.

Disaster Recovery as a Service (DRaaS) for UK small businesses

Tested failover targets, documented RPO and RTO, and runbooks that actually work when it matters. Enterprise-grade continuity, SMB-friendly price.

Cloud failover Image-level replication Annual test Written runbooks
01 / WHAT'S INCLUDED

Continuity,
end-to-end.

DR isn't a backup product with a better name. It's replicated compute, replicated network, and a tested plan for switching over.

01

Replicated workloads

Image-level replication of your critical VMs and servers to a UK cloud failover target. Continuous, not nightly.

02

Network & identity continuity

DNS, VPN and Entra ID access paths stay intact during failover so users sign in and work.

03

Written runbooks

Per-scenario runbooks: ransomware, site loss, platform loss, single-app loss. A junior engineer could follow it at 3 a.m.

04

Annual failover test

Full switchover to DR target, with your team observing. Report back on what worked, what didn't, and what we fixed.

05

Tabletop exercises

Quarterly walk-throughs with key staff so the plan isn't new to anyone when it's needed.

06

Documented RPO / RTO

Per-workload recovery objectives, written into your MSA. No vague "we'll do our best".

02 / HOW WE RUN IT

Design. Replicate.
Test. Repeat.

  1. PHASE 01

    Design

    Business impact analysis per system. Agree RPO / RTO. Size the failover target and network paths.

    • BIA workshop
    • RPO/RTO agreed
    • Runbook draft
  2. PHASE 02

    Replicate

    Stand up the failover target. Begin replication. Stabilise until RPO is consistently met.

    • Target built
    • Replication live
    • RPO verified
  3. PHASE 03

    Test

    First full failover test with your team. Find what doesn't work. Fix it. Sign off the runbook.

    • Failover test
    • Fixes applied
    • Runbook signed off
  4. PHASE 04

    Operate

    Continuous replication, quarterly tabletop exercises, annual full test. Runbook kept current as your environment changes.

    • Quarterly tabletop
    • Annual full test
    • Runbook maintained
03 / WHY IT MATTERS

Backup gets data back.
DR gets you trading.

A well-designed backup protects your data. A well-designed DR plan protects your ability to take orders, pay staff, and keep customers. If an hour of downtime costs you real money, DR is not optional.

  • Declared & running in hoursRTO in writing, rehearsed at least annually.
  • Tested, not hoped forA plan you haven't tested is a hope. Ours is a plan.
  • Cyber-incident readyRansomware playbooks included. Clean-room recovery path documented.
  • Board-grade reportingTest results, objectives met vs agreed, and gap register delivered in plain English.
PRIMARY DR TARGET REPLICATE · DECLARE · FAILOVER
04 / FAQ

Questions
we hear a lot.

What's the difference between backup and DR?

Backup gets your data back. DR gets your business running again. DR includes failover compute, networking and a tested runbook so a crippled environment can be brought back online within an agreed recovery time.

How often do you test the DR plan?

Full failover test annually, tabletop exercise quarterly. Both documented and signed off.

What RPO and RTO can we expect?

Standard RPO is 15 minutes for critical workloads, standard RTO is 4 hours. Both are per-workload and go into your MSA in writing.

Do we need DR if we already have good backup?

Most SMBs need both. Backup protects data; DR protects uptime. Which one you need more depends on how much lost revenue an hour of downtime represents.

What happens after a declaration?

We run the runbook with you. You talk to your customers; we talk to infrastructure. When the primary is ready, we run the failback cleanly.

NEXT STEP

Find out what
downtime would cost you.

One 30-minute session. We walk the workloads, ask the awkward questions, and tell you where the real risk sits.

RPO
15 min
RTO
4 hours
TESTED
Yearly