Backup & Resilience

Almost everyone has backups. Far fewer have restored from them recently, know how long a full recovery would take, or have checked that the backups are out of reach of the ransomware that would make them necessary. The gap is usually discovered on the worst possible day.

Databases and file stores that have never been restored end to end, backups reachable with the same credentials as production, cloud services assumed to be backed up by the provider, single region deployments, and recovery plans that exist as a document nobody has read since it was written.

We start with what the business can tolerate: how much data can be lost and how long systems can be down, per system. Then we design backups to meet those numbers: immutable copies, offsite or cross region, separated credentials, and coverage of the cloud services people forget. Restores are tested on a schedule, timed, and documented. For critical systems we design failover that has actually been exercised.

A resilience review of one to two weeks maps systems to recovery objectives and finds the gaps. Implementation follows in priority order. The first full restore test is done together, timed and written up. We leave you with a testing calendar, a recovery runbook per critical system, and, if you want it, a periodic test we run with you.

Recovery you have seen work, with the numbers to prove it.

• Recovery objectives per system and a resilience gap assessment
• Backup implementation with immutability, separation and offsite copies
• Tested restore procedures, recovery runbooks and a testing calendar

A ransomware incident becomes a recovery exercise instead of a negotiation, hardware or cloud failures become a known number of hours, and leadership can state the organisation's recovery capability with confidence.