Backup & Disaster Recovery
Plan for the bad day, then get on with the good ones
Fire, flood, ransomware, or someone deleting the wrong folder on a Friday — what decides whether it's a bad morning or a bad quarter is the work done beforehand.
What we protect
Copies you can trust, plans you can follow
Six pieces that add up to one answer: yes, we can get you back.
Servers & endpoints
Frequent, automated backups of servers and key laptops, with copies kept off-site and offline so ransomware can't reach them.
Microsoft 365 backup
Microsoft keeps 365 running; protecting your data in it is your job (it's in their terms). We back up mail, OneDrive, SharePoint and Teams independently.
Ransomware-resistant copies
Immutable storage and separated credentials, so an attacker who gets into your network can't also quietly destroy the backups.
A recovery plan on paper
Who does what, in what order, on the worst morning — written down, agreed with you, and reviewed as your business changes.
Restores, actually tested
We restore real files and systems on a schedule and record the results. A backup that's never been restored is a hope, not a plan.
Recovery times in hours, not acronyms
“How long until we're working again, and how much could we lose?” — agreed up front in hours and minutes, not acronyms.
“When did you last see one of your backups restore?”
If the answer is “never” or “when we set it up”, that's the gap. Our clients get restore test results on a schedule — evidence, not reassurance.
How we build it
From 'we should look at this' to a tested plan
Four steps, driven by what your business can and can't afford to lose.
- 1
Step 1
Map what matters
Which systems stop the business when they stop? Invoicing, email, the job-booking system — we rank them with you, because not everything needs the same protection.
- 2
Step 2
Set the numbers
For each system, two plain questions: how quickly must it be back, and how much recent work could you afford to lose? Those answers size the whole design.
- 3
Step 3
Build the protection
Backup schedules, off-site and immutable copies, and — where minutes matter — standby systems ready to take over.
- 4
Step 4
Test and repeat
Scheduled restore tests, an annual recovery rehearsal, and the plan updated when your systems change. Quiet, boring, dependable.
FAQ
Backups, restores and the bad-day plan
Microsoft 365, restore testing and the backup-versus-DR question.
Doesn't Microsoft already back up our 365 data?
Microsoft keeps the service running and protects against their failures — not against yours. Deleted mailboxes age out, retention has limits, and their own service agreement recommends third-party backup of your data. If a leaver's mailbox or a ransomware-encrypted SharePoint matters to you months later, you want your own copy.
What's the difference between backup and disaster recovery?
Backup is the copy; disaster recovery is the plan for using it under pressure. A backup answers “is our data safe?”; DR answers “it's 9am, the server room flooded — who does what, and when are we invoicing again?” We build both, because one without the other fails on the day.
How often would you test our restores?
Automated verification runs continuously, real restore tests run on a schedule we agree (monthly spot-checks are typical), and we recommend a fuller recovery rehearsal annually. You see the results — including anything that failed and what we changed.
We already have a backup 'thing' running. Is that enough?
Possibly! The questions that decide it: does it cover everything that matters (including 365)? Could ransomware reach the copies? When did anyone last restore from it? We'll audit it honestly — if it's good, we'll say so and leave it alone.
What does this cost for a business our size?
It scales with how much data you have and how fast you need to be back. The audit gives you a fixed monthly price — typically a small fraction of what a single day of downtime would cost you in lost work alone.
Talk to us
Find out if your backups would save you
Ask for a recovery audit: what's covered, what isn't, and whether your copies would survive a ransomware incident.
If what you already have is good, the audit says so — and we leave it alone.