CLOUD / RESILIENCE & DR
Recovery you have tested
We design backup, failover and disaster recovery on AWS, Microsoft Azure and Google Cloud to the targets you set, then test it with your team.
A backup that has never been restored is a hope, not a plan. We agree how long each system can be down and how much data it can lose, design to those targets using each cloud’s own zones, regions and recovery services, and then prove it with a test your team runs.
What we do
Recovery targets
Without agreed targets, every system gets the same treatment. We set recovery time and recovery point objectives per system, with the business.
Backup design
Backups are often incomplete or stored next to what they protect. We design backup policies, retention and isolation per system.
Failover and multi-region design
A single zone or region is a single point of failure. We design zone-redundant and cross-region failover where the targets need it.
Recovery testing
Untested runbooks fail under pressure. We run recovery tests with your team and fix what they reveal.
Our solutions
A look at how your current platform would cope with a zone, region or data loss event, and what to fix first.
- Recovery targets agreed per system
- Gaps against those targets
- A prioritized remediation plan
Backup and failover designed and built using services such as AWS Elastic Disaster Recovery, Azure Site Recovery or Google Cloud Backup and DR Service.
- Backup and failover design
- Infrastructure as code for the recovery environment
- Runbooks for each recovery scenario
Scheduled tests that show whether recovery works, how long it takes and what breaks along the way.
- Test plan agreed with system owners
- Recovery run with your team
- Findings fixed and the test repeated
How it runs
Set targets
We agree recovery time and recovery point objectives for each system with its owners.
Design
We design backup, redundancy and failover to meet those targets at a cost you accept.
Build
We build it as code. Any cutover is planned for minimal disruption, with tested rollback.
Test
We run a recovery test with your team, fix what it finds, and schedule the next one.
What you get
- Recovery targets agreed and written down for each system
- Backup and failover design, documented
- Runbooks for each recovery scenario
- A recovery test run with your team, and its results
- A schedule for testing again
Questions we get asked
Does every system need multi-region failover?
No. Most do not. We match the design to the recovery targets for each system, so you only pay for redundancy where the business needs it.
Can you recover from on-premises into the cloud?
Yes. The cloud can act as a recovery site for on-premises systems, which is also a common first step toward migration.
How often should we test recovery?
At least once a year for each critical system, and after any major change. We help you set a schedule your team can keep.