Backup and Disaster Recovery
Most businesses have backups. Far fewer have backups that have ever been restored from. The gap between those two things is where companies discover, during the worst week of their existence, that the job has been silently failing since March.
What we do
Backups you have actually proven work
A backup is a theory until someone restores from it. We test, and we show you the results.
Automated Backup
Servers, workstations, and cloud data on a schedule built around how much work you can afford to lose. Monitored, with failures raised as alerts rather than sitting unread in a log.
Immutable and Offsite Copies
Copies that ransomware cannot encrypt or delete, held offsite. Modern ransomware hunts for backups first, and attackers know that destroying them is what forces payment.
Tested Restores
Scheduled test restores with documented results. This is the step almost everyone skips, and it is the only thing that converts a backup into a recovery capability.
Recovery Objectives
We establish how much data loss and how much downtime your business can actually absorb, then build to those numbers instead of to whatever the software defaults to.
Microsoft 365 Backup
Email, SharePoint, OneDrive, and Teams backed up independently of Microsoft. Their retention window is far shorter than most businesses assume and is not designed as a recovery tool.
Documented DR Plan
Who does what, in what order, with what credentials. During an outage nobody improvises well, and the plan needs to be readable by someone who is not you.
How we build recovery
Start from what an outage actually costs you, then work backward to the design.
Assess
What data matters, where it lives, what is currently protected, and what is quietly not. Most reviews surface at least one significant gap.
Design and Deploy
Backup architecture built to your recovery objectives, with offsite and immutable copies and monitoring that alerts on failure.
Test and Report
Scheduled restore testing with results you can show to an auditor, an insurer, or a board.
When did you last restore from backup?
If the answer is never, or you are not certain, a backup review is worth an hour. It is the cheapest insurance in IT.
FAQ
Backup questions we get asked
It is better than nothing and it is not sufficient. A drive attached to the machine it protects gets encrypted alongside it during a ransomware event, and a drive in the same building burns in the same fire. You need at least one copy offsite and at least one copy the attacker cannot reach.
Three copies of your data, on two different types of media, with one copy offsite. It has held up for decades. The modern addition is that one copy should be immutable, meaning it cannot be altered or deleted even by someone holding valid credentials.
Quarterly at minimum for critical systems, and after any significant infrastructure change. Testing is the part that gets skipped, and it is the part that determines whether you actually recover. Failed backup jobs can run unnoticed for months.
Yes, and this surprises people. Microsoft protects the service, not your data from your own mistakes. Deleted items and retention windows are short, and a ransomware event that syncs to OneDrive will propagate. Independent backup of 365 is standard practice for good reason.
That is your recovery time objective, and it is a business decision before it is a technical one. Faster recovery costs more. We ask what an hour of downtime actually costs you, then design to a target that makes financial sense rather than selling you the most expensive option available.
