Services / Backup & recovery
A backup is a restore that worked.
We design backups around the question that matters — how long can you be down and how much can you lose — then prove the answer every month with a real restore.
Who this is for
Any organization whose data is its business: client files, patient records, designs, accounting systems, email. Also anyone who has a backup job that reports success and has never been restored from.
The deliverable is a written recovery plan with numbers in it (recovery time objective, recovery point objective, per system), the infrastructure to meet those numbers, and a monthly report showing the test restore passed.
What's included
- Recovery objectives workshop: RTO/RPO per system, agreed and written down
- 3-2-1 design: local copy, off-site copy, one copy immutable or offline
- Server and VM image backups with bare-metal and instant-VM recovery
- Workstation backups for the machines that actually hold data
- Microsoft 365 / Google Workspace backup
- Ransomware-resistant storage: immutability, separate credentials, air gap where justified
- Daily monitoring of every job; failures become tickets, not surprises
- Monthly test restore, documented, in your report
- Annual full disaster recovery exercise
- Disaster recovery runbook: who does what, in what order, with which credentials
- Retention policies that meet your legal and contractual requirements
- Decommissioning of old backup media securely
How an engagement runs
- Objectives
Half a day deciding what downtime and data loss actually cost you, system by system.
- Design and build
Backup targets, software, schedules and immutability configured to hit those numbers.
- Prove it
First full restore test with you watching; runbook written from what we actually did.
- Keep proving it
Monthly automated test restores and an annual exercise, results in your report.
Common questions
Isn't our cloud provider backing us up?
Usually not in the way you think. Microsoft and Google protect against their own hardware failure, not against your deletion, a compromised account or ransomware syncing encrypted files.
How fast could we be back?
Depends on what we design for. Hours for an instant-VM recovery, days for a cold rebuild. That's why we agree the number first and then price the design that meets it.
What about ransomware?
Immutable copies that the attacker's credentials can't touch, plus tested restores, are the difference between a bad day and a closed business.
Can you take over an existing backup system?
Yes — we'll test a restore first, which is usually the moment the conversation changes.
Tell us what's broken, or what you want built.
Describe it in a sentence or two. You'll get a straight answer about whether we can help, usually the same business day.