The short answer
Backups fail in ransomware attacks because attackers delete them first, because they were never tested, or because restores take far longer than the business can tolerate. Follow the 3-2-1-1-0 rule, make at least one copy immutable, use separate credentials for backup systems, set RTO and RPO per system and run restore tests every quarter.
Why backups fail
| Failure | Fix |
|---|---|
| Backups deleted with stolen admin credentials | Separate backup accounts, MFA, immutable storage |
| Systems missing from backup | Inventory and backup coverage reports |
| Never tested, corrupt or incomplete | Quarterly restore tests |
| Restore takes days | RTO-based design and recovery runbooks |
| Malware restored with the data | Clean recovery environment and scanning |
| SaaS data not backed up | Backups for Microsoft 365, Google Workspace and key SaaS |
A simple test plan
- List critical systems and agree RTO and RPO for each with business owners.
- Check coverage: every critical system and SaaS app has a backup and an owner.
- Make one copy immutable and isolated from production identities.
- Restore quarterly: a file, a database and a full server or cloud workload.
- Time it and compare against RTO; fix bottlenecks.
- Run a yearly recovery exercise simulating ransomware, including communications and decision-making.
- Keep evidence for SOC 2, ISO 27001, HIPAA and cyber insurers.
How Zuroth helps
- Backup and disaster recovery from $1,500 a month with immutable copies and tested restores.
- 24/7 managed detection and response to stop ransomware early.
- Managed cloud services with recovery built into the architecture.
Our hospital network case study shows clinical systems restored in 4 hours in drills, down from 3 days.
Next step: book a free consultation.
Related reading
- Managed Security & Cloud services
- SOC as a Service vs MDR vs MSSP
- Cloud cost optimization quick wins
- Backup & disaster recovery
- Managed detection & response
Frequently asked questions
Why do backups fail during ransomware attacks?
Attackers often find and delete or encrypt backups first, using the same admin credentials they stole for production. Other failures include backups that were never tested, missing systems, restore times far longer than the business can tolerate and infected data restored back into production.
What is the 3-2-1-1-0 backup rule?
Keep at least three copies of data, on two different types of media, with one copy offsite, one copy offline or immutable, and zero errors verified through regular restore tests. It extends the classic 3-2-1 rule for ransomware.
What are immutable backups?
Immutable backups can't be changed or deleted for a set retention period, even by administrators. Cloud object lock features and hardened backup appliances provide immutability, so ransomware and attackers with stolen credentials can't destroy your recovery points.
What are RTO and RPO?
The recovery time objective (RTO) is how long a system can be down before the impact is unacceptable. The recovery point objective (RPO) is how much data, measured in time, you can afford to lose. Both should be set per system by the business and drive backup design.
How often should we test restores?
Test critical systems at least quarterly and after major changes, with a full recovery exercise at least once a year. Measure actual restore times against RTO, check data integrity and record results as evidence for auditors and cyber insurers.