Disaster recovery (DRP) test
Test restoring your backups before you need them.
A green light tells you a copy was made. It does not tell you whether everything can be restored, or how long it takes. We run the test in an isolated space and give you the result in writing.
Source
File server
Copied every night
Check
Restore test
In an isolated space, on a scenario chosen with you
Result
Data recovered
Files opened and permissions checked
✕The accounting database was missing from the copy: the gap is reported, then fixed.
These are example mechanisms, not client projects.
How it works
What happens after your request
- 1Choose what needs to be recovered
Together we select representative data, a mailbox, service, machine or folder and an isolated location where the restore can be tested safely.
- 2Run the scenario without affecting production
The restore follows the available procedure and access path. Timings, errors and dependencies are recorded during the test.
- 3Confirm that the result is readable and usable
We check the agreed files, permissions and application elements. The report separates what worked, what remains uncertain and what needs correction.
- 4Correct the recovery plan and choose a useful frequency
Corrections are ordered by impact. The test can remain a one-off exercise or be repeated after a significant change and at an agreed interval.
Starting point
Restore test (DRP)
The disaster recovery (DRP) test your backup may never have had. We restore the chosen data in an isolated space, without touching production, and measure how long it takes to get back to work.
Precaution
The test is prepared with the person responsible for the data
No destructive restore starts without explicit approval. The limits of the test and the data involved are agreed before the work begins.
Which backup do you want to put to the test?
Tell us which solution you use, which data matters most and when it was last tested. We will propose a scenario that fits the environment.
Prepare a restore test