The Vanishing Backups
How a 45-person architecture firm lost three years of work because their MSP never tested backup restores.
The Company
Fairview Architecture is a 45-person firm specializing in commercial building design. They had been with their MSP for over five years, paying approximately $8,500 per month for comprehensive IT services—including what they believed was enterprise-grade backup protection.
The managing partner trusted the MSP completely. Tickets were answered promptly. Systems ran smoothly. The monthly invoice included a line item for “Backup & Disaster Recovery Services.” Everything seemed fine.
The Disaster
On a Tuesday morning in March, the firm’s primary file server crashed. The hard drive failure was catastrophic—three years of architectural drawings, project files, client correspondence, and financial records were on that server.
The managing partner called the MSP immediately. “No problem,” they said. “We’ll restore from backup. Give us a few hours.”
Those few hours turned into days. Then a week. Then the truth came out: there were no backups.
What They Discovered
The backup software had been running for three years. It reported success every night. The MSP’s monitoring dashboard showed green checkmarks.
But the MSP had never tested a restore. The backup job was writing to a network location that didn’t exist. For three years, the software reported success while backing up… nothing.
When the server crashed, there was nothing to restore.
The Cost Breakdown
Direct Financial Losses: $185,000
- $65,000: Data recovery services (partially successful)
- $45,000: Staff time reconstructing lost project files
- $35,000: Lost billable hours during recovery period
- $25,000: Client relationship damage and concessions
- $15,000: Legal review and new MSP onboarding
But the financial cost doesn’t capture the full impact:
- Three major client relationships were damaged when project files couldn’t be recovered
- Two junior architects left the firm during the crisis, citing stress and uncertainty
- The managing partner spent six months dealing with the fallout instead of growing the business
- The firm’s reputation in their market was permanently affected
What Went Wrong
Backup software can report success even when backups are failing. The only way to verify backups work is to regularly test restoring files. The MSP had a monitoring dashboard showing green checkmarks—but nobody ever tried to actually restore a file.
The firm received monthly invoices showing “Backup Services” as a line item. But they never received reports showing what was backed up, success rates, or test restore results. They had no way to verify the work was being done.
In five years, the MSP never conducted a single QBR. There were no strategic meetings to discuss backup procedures, test results, or disaster recovery planning. The relationship was purely reactive—tickets got answered, but nothing was validated.
The backup job was misconfigured from day one—writing to a network path that didn’t exist. A simple quarterly audit would have caught this immediately. But audits were never part of the service.
How This Could Have Been Prevented
✓ Preventive Measures That Would Have Caught This
- Monthly backup reports showing success rates, backup sizes, and what’s being backed up
- Quarterly test restores documented and provided to the client
- Quarterly business reviews discussing backup strategy and recent test results
- Configuration audits verifying backup jobs are writing to valid locations
- Offsite/cloud backup verification ensuring redundant copies exist
Any one of these measures would have caught the problem. The firm would have discovered the backup failure within 90 days instead of three years later.
The Aftermath
Fairview Architecture fired their MSP immediately and hired a new provider. The new MSP conducted a complete infrastructure audit and implemented proper backup procedures with monthly test restores.
The managing partner now receives:
- Monthly reports showing backup success rates and storage utilization
- Quarterly test restore reports with screenshots proving data can be recovered
- Quarterly business reviews discussing IT security, upcoming needs, and strategic planning
- Complete documentation of their network, backup procedures, and disaster recovery plan
But the $185,000 loss and three years of trust couldn’t be recovered.
Don’t Let This Happen to Your Business
Use My IT Support Report Card to verify your backups are working. Our assessment includes specific questions about backup testing, restore procedures, and documentation.
Key Takeaways
What Business Owners Should Learn
- “Backup services” on an invoice doesn’t mean backups are working. You need proof.
- Monitoring dashboards can lie. Green checkmarks mean the software ran—not that data is recoverable.
- Test restores are the only proof. If your MSP isn’t regularly testing restores and showing you the results, your backups might not work.
- Quarterly business reviews should discuss backups. When was the last restore test? What’s the recovery time objective? Is offsite backup confirmed?
- Documentation matters. Monthly reports showing what’s backed up, success rates, and storage trends help you verify the work.
Questions to Ask Your MSP Today
If they can’t give you a specific date within the last 90 days, that’s a problem. Ask to see documentation of the test restore.
Reports should show what’s being backed up, success/failure rates, backup sizes, and any issues that were resolved.
You need both local backup (for fast restores) and offsite/cloud backup (for disasters like fire, theft, or ransomware).
They should be able to give you specific timeframes for different scenarios. Vague answers like “pretty quickly” are red flags.
A professional MSP will welcome this request. Defensive or dismissive responses are warning signs.
If your MSP can’t answer these questions confidently with documentation, you might be in the same situation Fairview Architecture was—paying for backup services that don’t actually work.