08 · Backup & RecoveryContinuity

Backup & Cyber Recovery

A backup is a belief until it has been restored. Ransomware changed what the job is: the copy now has to survive an attacker who has the same administrative rights as your backup operator, which rules out most of what was adequate ten years ago. We design for that attacker, and we make the restore a rehearsed procedure with a measured duration rather than a number in a policy.

IMMUTABLE BACKUP
AIR GAP
REPLICATION
RTO / RPO
DR RUNBOOKS
RESTORE TESTING

Reference schematic08/09

Capabilities

What this covers.

01
Backup Architecture
Retention and placement designed against a stated recovery objective, sized on real change rates rather than a licence count.
02
Immutability & Air Gap
Copies that cannot be altered or deleted inside their retention window, including by an account that has taken over the backup console.
03
Disaster Recovery Design
Recovery sequence by dependency, not by alphabet, with the runbook written so the person holding it at 03:00 is not the person who designed it.
04
Recovery Testing
Scheduled restores into an isolated environment, timed and documented, so the recovery time objective is a measurement instead of an aspiration.

Outcomes

What you have at the end of it.

01
A restore time measured in a test, not estimated
02
Backup copies an attacker with admin rights cannot delete
03
A recovery runbook ordered by dependency

Platforms we use here

The platforms we design, deploy and operate, grouped by the job each one does. Selection follows the requirement rather than a reseller agreement, and nothing here is a claim to any vendor's partner programme — it is a statement of what our engineers work in.