Backups Nobody Tests Aren't Backups.
Business continuity for Dallas–Fort Worth businesses that need to survive ransomware, hardware failure, or a bad Tuesday. Immutable backups, verified restores, and a written recovery time — not a wish.
Most Backups Fail on the Only Day They Matter.
Every business has a backup. Almost none of them work when they need to. The tape drive was full. The cloud sync stopped in March. The Veeam job was pointing at a disk that got repurposed. The Microsoft 365 licenses don't cover what the client thinks they cover.
You find out on the worst day of the year — the day the CryptoLocker variant finishes encrypting your file server, or the day the SAN controller dies, or the day the CFO deletes the wrong folder and empties the recycle bin.
Real backup and recovery is boring on purpose. It runs on a schedule you don't watch, into storage the attackers can't reach, tested monthly by a human, with a written recovery time that the CFO signed off on. That's what we build.
Backups you hope work
- Backup jobs nobody watches
- No immutable / air-gapped copy
- Microsoft 365 assumed "backed up"
- Restore has never been tested
48 Technologies backup
48 Technologies backup- Immutable copies attackers can't touch
- Monthly restore drills with proof
- Microsoft 365 backed to third-party vault
- Written RTO/RPO in the contract
Four Layers Between You and "We Lost Everything."
One backup product is a single point of failure. Real business continuity is four independent layers, each covering what the last one missed.
Endpoint & server
- Image-based backup of every server
- File-level backup of every endpoint
- Hourly snapshots for hot data
- Encrypted at rest and in transit
Microsoft 365 & SaaS
- Third-party M365 backup (Exchange, OneDrive, SharePoint, Teams)
- SharePoint versioning beyond Microsoft's window
- Google Workspace where applicable
- Retention that meets your compliance rule
Immutable & offsite
- Immutable object storage (WORM)
- Second geographic region minimum
- Air-gapped from production credentials
- Ransomware can't encrypt or delete
Recovery & DR runbook
- Monthly test restore, with sign-off
- Documented recovery order
- Vendor and contact list current
- Board-ready DR posture summary
From "I Think We Have Backups" to Signed RTO.
Backup and recovery isn't a product install — it's a system with an owner, a runbook, and a proven restore. Here's how we get there in 45 days.
What you have. What you think you have.
Inventory every backup job, every retention policy, every restore point. Compare against what leadership assumes is protected. The gap is usually shocking.
- Current backup inventory
- Microsoft 365 coverage audit
- Retention vs. compliance check
- Written gap report
Stand up the four layers.
Endpoint & server backup product deployed and tuned. M365 third-party backup licensed and syncing. Immutable offsite storage configured. DR runbook drafted with your team.
- Backup agent deployment
- M365 backup activation
- Immutable offsite storage
- Draft DR runbook
Test restore. Then sign the RTO.
A live restore of a server, a mailbox, and a SharePoint site. Timed against the RTO in the contract. If any restore misses, we fix it before you sign.
- Live restore drill (server + mailbox + site)
- RTO/RPO measured against contract
- Signed leadership sign-off
- Monthly restore drill scheduled
Per Workload, Per Terabyte, No Games.
Backup pricing has three moving parts: how many workloads (servers, endpoints, M365 seats), how much data (terabytes retained), and how far back (retention period). We price all three transparently — you never see a surprise storage overage. Most SMB engagements land between $12 and $28 per user per month for full-stack backup (endpoints + M365 + immutable offsite), separate from server-specific pricing.
-
1. 1. Workload count & mixServers, endpoints, Microsoft 365 seats, and cloud workloads price separately. We inventory the actual mix, not a headcount guess.
-
2. 2. Data volume & retention30 days of point-in-time is different from 7 years for compliance. Retention drives storage cost more than daily data volume does.
-
3. 3. Recovery time expectationsA 4-hour RTO costs more than a 24-hour one. We price to your business tolerance, not to the vendor's highest tier.
Consumer/Cloud Sync vs. 48 Technologies vs. DIY Enterprise
Three ways to "do backup" at a 25–150 employee DFW business. Only one of them will actually restore on the day it matters.
Sync / Cloud-Only
- Sync ≠ backup (deletes propagate)
- Ransomware encrypts the sync too
- No point-in-time recovery
- M365 native retention insufficient
- No immutable / air-gapped copy
- Nobody tests restore
48 Technologies Backup
- Immutable offsite object storage
- M365 third-party backup included
- Monthly tested restore with sign-off
- Written RTO/RPO in the contract
- Ransomware-resistant by design
- One vendor, one bill, one owner
DIY Enterprise Stack
- $40K+ software + hardware upfront
- Requires FTE to run it correctly
- License renewals + storage overages
- Test-restore process nobody owns
- Overkill for 25–150 employee firms
- Great — if you have a backup admin
At Lehman we ran backups like the company depended on them, because it did. I moved that same discipline down to businesses that can't afford a $10M outage — because they really can't afford a $10K outage either.
Do You Actually Know If Your Backups Work?
30 minutes on the phone. Bring the name of your backup product and your last restore date. We'll tell you honestly where you stand.