DR Testing
A plan that has never been tested is a hypothesis. AS runs DR tests that are realistic enough to find problems and controlled enough not to cause them.
When you need this
- Plan exists but has never been exercised
- Backup restores tested for files only, never whole systems
- Auditors or insurers require evidence of testing
- Major changes to infrastructure since the last test
- New staff have never been through a recovery
What we do
Tabletop exercises
Walk-through of a scenario with the people who'd handle it, exposing gaps in roles, information and decisions.
Restore tests
Real restores of systems, databases and VMs into isolated environments, timed against objectives.
Failover tests
Controlled failover of replicated or clustered systems where in place.
Results and remediation
Documented outcomes, measured against RTO/RPO, with a fix list.
How it works
- Step 1
Assess
Understand the environment, the risks that matter and what a disruption would actually cost.
- Step 2
Protect
Put the right backups, isolation and safeguards in place — and verify they work.
- Step 3
Recover
When something fails, recover data from the safest, most complete sources first.
- Step 4
Restore
Bring services back in business-priority order on clean, trusted infrastructure.
- Step 5
Validate
Confirm data integrity, application function and that the cause has been dealt with.
- Step 6
Improve
Close the gaps the incident exposed and update the plan.
What affects the outcome
Outcomes are never guaranteed. Every case is assessed on its own condition, and we tell you what is realistic before you commit.
- Whether backups exist, are complete and were verified before the incident
- How isolated backups and snapshots were from the systems that failed
- Documentation of the environment: dependencies, credentials, configurations
- Time since the incident and what has been changed since
- Availability of clean infrastructure to restore onto
Frequently asked questions
Will testing disrupt production?
Tests are designed to run in isolation. Any step with production impact is agreed in advance and scheduled.
How often should we test?
At least annually for a full rehearsal, with restore tests more frequently. The right cadence depends on how quickly the environment changes.
Related services
Not sure what you're dealing with?
Describe the situation and we'll tell you what's realistic.