🕑 Estimated reading time: 4 minutes  |  Last updated: May 22, 2026

Ransomware gangs routinely try to delete or encrypt backups before striking. To survive, follow the 3-2-1-1-0 rule: three copies of data, on two types of media, one off-site, one offline or immutable (unchangeable for a set period), and zero errors after verification and test restores. Separate backup credentials from your main network, protect backup consoles with MFA, back up SaaS data such as Microsoft 365 and Google Workspace, and rehearse full recovery, not just file restores.

A rack of servers in a server room

Ask a ransomware incident responder what separates organisations that recover in days from those that struggle for months, and you will often hear one word: backups. Not just having them, but having backups that the attackers could not reach, that actually work, and that the team knows how to restore quickly.

Criminals know this too. In many attacks, they spend time inside a network specifically to find and destroy backups before deploying ransomware, because victims without backups are more likely to pay.

From 3-2-1 to 3-2-1-1-0

The classic 3-2-1 rule has been updated for the ransomware era:

What “Immutable” Really Means

An immutable backup cannot be modified or deleted for a defined retention period, even by an administrator. Many backup products and cloud storage services offer object lock or similar features. If an attacker steals admin credentials, they still cannot wipe those copies before the lock expires. Make sure the setting is genuinely enforced (some modes can be overridden by privileged users) and that retention covers the time it might take to discover an intrusion.

Isolate Your Backup System

Do Not Forget Cloud and SaaS Data

Many businesses assume Microsoft 365, Google Workspace or their CRM provider backs up everything for them. Providers keep their services running, but under the shared responsibility model, protecting against accidental deletion, malicious insiders or account compromise is often your job, and built-in retention can be limited. Consider dedicated SaaS backup tools for email, files and business-critical apps.

What Should You Back Up?

Testing: The Step Everyone Skips

A backup is only as good as your last successful restore. Build a testing routine:

  1. Monthly: restore a sample of files and confirm they open.
  2. Quarterly: restore a full system or database to an isolated environment.
  3. Annually: run a full disaster recovery exercise, timing how long it takes to bring critical services back.

Measure against your recovery time objective (how quickly you need systems back) and recovery point objective (how much data you can afford to lose). If restoring takes two weeks and the business can only survive three days, you have a gap to fix.

Restore Into a Clean Environment

When recovering from ransomware, the danger is restoring systems that still contain the attackers’ backdoors, or restoring backups taken after the initial compromise. Work with incident responders to identify when the intrusion began, scan backups before restoring, rebuild identity systems carefully and reset credentials.

For Small Businesses

You do not need enterprise gear. A reputable cloud backup service with versioning and immutability, plus an external drive that is disconnected after each backup, gives you strong protection. Write down exactly how to restore, and test it.

Prove you can restore from an isolated backup

Backups are your best answer to ransomware, but only if attackers cannot reach them and you can restore quickly. Follow 3-2-1-1-0, isolate your backup system, include cloud data, and practise recovery until it is routine. Then a ransom note becomes a disruption, not a disaster.

Frequently Asked Questions

Is cloud sync, like OneDrive or Google Drive, a backup?

Not on its own. Sync can replicate deletions or encrypted files; use versioning and a separate backup.

How long should we keep backups?

Long enough to cover the time it might take to discover an intrusion, often several weeks or months, plus any legal retention requirements.

How often should we back up?

As often as your business can tolerate losing data; for critical systems that may be hourly or continuous.

Leave a Reply

Your email address will not be published. Required fields are marked *