IT & Cloud

The 3-2-1 Backup Rule — A Ransomware-Resilient Backup Plan

How the 3-2-1 backup rule works, why sync tools are not backups, and how immutable copies and restore testing protect your business from ransomware.

Ransomware does not just encrypt your files — modern attacks deliberately hunt for your backups first. A backup plan that worked ten years ago can fail completely today. The 3-2-1 rule, updated with a few modern safeguards, is still the simplest way to stay safe.

The 3-2-1 rule

  • 3 copies of your data — the live data plus two backups.
  • 2 different types of storage — for example a local backup device and cloud storage.
  • 1 copy off-site — somewhere a fire, theft or flood at your office cannot reach.

Many teams now extend this to 3-2-1-1-0:

  • 1 copy immutable or offline — it cannot be changed or deleted, even by an administrator account, for a set period.
  • 0 errors — backups are verified and restores are tested.

“But everything is already in the cloud”

File-sync tools like shared drives are excellent for collaboration, but they sync mistakes too. If ransomware encrypts files on a laptop, or someone deletes a folder, that change can be copied everywhere. Cloud email and productivity suites also have limited retention for deleted items. You still need independent, versioned backups.

What to back up

  • File servers and shared drives
  • Databases and business applications (accounting, ERP, e-commerce)
  • Email and cloud productivity accounts
  • Website files and databases
  • Configuration of firewalls, servers and cloud infrastructure

Recovery targets

Agree two numbers for each important system:

  • RPO (Recovery Point Objective) — how much data you can afford to lose. One day? One hour?
  • RTO (Recovery Time Objective) — how long you can afford to be down.

These numbers decide how often you back up and how your recovery is designed.

Test restores — on a schedule

The most common backup failure is discovered on the day you need it. Schedule restore tests at least quarterly for critical systems: restore a database, a mailbox and a few files, and time how long it takes. Write down the steps so anyone on the team can follow them under pressure.

Protect the backups themselves

  • Separate backup credentials from everyday admin accounts, protected with MFA.
  • Encrypt backups in transit and at rest.
  • Monitor backup jobs and alert on failures.
  • Keep at least one copy where ransomware on your network cannot reach it.

Not sure your backups would survive a bad day? Our backup & disaster recovery service designs, tests and documents it for you — contact us for a review.

backupransomwaredisaster recovery3-2-1 rule