What RTO and RPO targets can you meet?

It depends on your budget and architecture. We design for the targets you specify after understanding what those targets cost to achieve. Common targets we engineer for: 15-minute RTO, 5-minute RPO for tier-1 systems.

Do you test the DR plan or just write it?

We require at least one live restore test before closing any DR engagement. A runbook that has never been tested is documentation, not disaster recovery.

Can you work with our existing backup vendor?

Yes. We work with Veeam, Commvault, Restic, Barman, and most enterprise backup platforms. The engagement is vendor-agnostic -- we assess what you have and fill the gaps.

How often should DR plans be tested?

At minimum annually, with a full restore test. For tier-1 systems in regulated industries, quarterly table-top exercises and semi-annual live tests are the standard we recommend.

Disaster Recovery -- Backups, Failover & Runbooks

Backup systems, failover architecture, and documented runbooks with tested recovery time objectives. We define RTO and RPO targets before signing -- not after an incident reveals what was never tested.

What we deliver

Backup audit: current state, retention gaps, and untested restore paths identified
Multi-tier backup architecture: local, offsite, and cloud targets for each workload class
Failover design: active-active or active-passive, scoped to your actual downtime tolerance
Disaster recovery runbook: step-by-step restore procedures for each system tier
Annual DR test with written results and gap remediation plan

Every DR engagement includes at least one live restore test before the engagement closes. Documented results go to your team.

You find out your recovery works during a scheduled test, not during an incident.

Why teams choose Cobham for disaster recovery

Targets agreed before signing. RTO and RPO are defined up front, not discovered after an outage.
At least one live restore test before close. An untested backup is treated as no backup.
Multi-tier by design. Local, offsite, and cloud targets scoped to your actual downtime tolerance, not a template.

How we engage

Principal-led. Fixed-scope.

Every Disaster Recovery engagement is scoped before the contract is signed. Two principals. No subcontractors. No account managers between you and the work.

Discovery call

30 minutes. We map your current state, identify the constraints, and tell you what we would do first. No obligation and no invoice.

Scoped brief

A written brief defining deliverables, duration, and a fixed price. If we cannot define the output, we do not take the engagement.

Execution & handoff

Principal-delivered work with a documented handoff. Runbooks, IaC, and access handed to your team at close. You own everything.

Common questions

Frequently asked.

What RTO and RPO targets can you meet?: It depends on your budget and architecture. We design for the targets you specify after understanding what those targets cost to achieve. Common targets we engineer for: 15-minute RTO, 5-minute RPO for tier-1 systems.
Do you test the DR plan or just write it?: We require at least one live restore test before closing any DR engagement. A runbook that has never been tested is documentation, not disaster recovery.
Can you work with our existing backup vendor?: Yes. We work with Veeam, Commvault, Restic, Barman, and most enterprise backup platforms. The engagement is vendor-agnostic -- we assess what you have and fill the gaps.
How often should DR plans be tested?: At minimum annually, with a full restore test. For tier-1 systems in regulated industries, quarterly table-top exercises and semi-annual live tests are the standard we recommend.

Related services

Other categories we operate.

Cloud

Disaster Recovery

Talk to a principal.

Schedule a 30-minute call. We map your current state, identify the highest-leverage next step, and give you a written scope before you sign anything.

Schedule a call →

Direct to a principal · Response under four hours

Disaster Recovery.