Disaster Recovery
Disaster Recovery Design and Tested Restores
Many businesses have backups. Fewer have ever restored from them. That gap is where companies find out, during the worst week they have had, that the backup job has been failing quietly for months. We design recovery and prove it works.
What we deliver
Recovery You Have Watched Work
A backup is a theory until someone restores from it. Every project ends with a restore test and the results in writing.
Recovery Objectives
How much data loss and how much downtime your business can absorb, agreed in writing and used as the design target instead of whatever the software defaults to.
Backup Architecture
Servers, workstations and cloud data covered on a schedule built around those objectives, with alerting on failed jobs routed to whoever runs your systems.
Immutable and Offsite Copies
Copies held offsite and immutable in compliance mode (for example object lock), so they cannot be encrypted or deleted before their retention date, even with admin credentials. Many ransomware variants look for backups first, because destroying them is what forces payment.
Microsoft 365 Backup Design
Email, SharePoint, OneDrive and Teams backed up independently of Microsoft, with retention set to your real needs.
Restore Testing
A restore test of your critical systems at the end of every project, with documented results you can show an insurer, auditor or board. Repeat tests can be scheduled as follow-on projects.
DR Plan and Runbook
Who does what, in what order, with which credentials. Written so someone other than you can follow it during an outage.
How a Disaster Recovery Project Runs
Start from what an outage costs you, then work backward to the design.
Assess
What data matters, where it lives, what is protected now and what quietly is not.
Design and Build
Backup architecture built to your recovery objectives, with offsite and immutable copies and alerting on failures.
Test and Hand Over
A real restore test, the DR runbook, and a walkthrough for whoever will run it. Pairs well with incident readiness work.
When Did You Last Restore From Backup?
If the answer is never, or you are not sure, a 30-minute call is the cheapest place to start.
FAQ
Disaster Recovery Questions We Get Asked
It is better than nothing and it is not enough. A drive attached to the machine it protects gets encrypted with it, and a drive in the same building burns in the same fire. You need at least one offsite copy and one copy an attacker cannot reach.
Three copies of your data, on two types of media, with one copy offsite. The modern addition is that one copy should be immutable, meaning it is locked in compliance mode (for example object lock) so it cannot be deleted before its retention date, even with admin credentials.
At least quarterly for critical systems, and after any significant infrastructure change. We run the first test as part of the project and can schedule repeat tests as short follow-on projects.
Whoever runs your systems: your internal staff or your current IT provider. We set up the alerting and the runbook so failed jobs are noticed and handled.
Yes. Standard Microsoft 365 plans do not include backup. Built-in recycle bins and retention cover recent mistakes, and ransomware-encrypted files sync to OneDrive like any other change. Backup, through Microsoft's add-on or a third-party tool, gives you a copy with its own retention that you control.
That is your recovery time objective, and it is a business decision before a technical one. Faster recovery costs more. We ask what an hour of downtime costs you, then design to a target that makes financial sense.
