Glossary · simply explained

3-2-1 backup rule

The 3-2-1 rule is the proven rule of thumb of data protection: at least three copies of the data (original plus two backups), on two different media types, one copy of which is kept at another location. It protects against the most common loss scenarios — hardware failure, operator error, fire, theft.

Against ransomware the classic scheme alone is no longer enough: attackers deliberately encrypt reachable backups too. Modern variants therefore extend to 3-2-1-1-0 — additionally one offline or immutable copy and zero errors in regular restore testing.

The rule in detail

Three copies means: the original counts, plus two independent backups — independent also meaning: not on the same storage, not in the same failure domain. Two media types separate failure classes, say disk and object storage or disk and tape; a firmware bug or controller defect then does not hit both.

The off-site copy separates spatially: another data center, another fire compartment, the cloud. Logical separation matters just as much — separate credentials, a separate administration domain. A backup reachable with the same admin credentials as production falls with it.

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

  • The additional 1: one copy offline (air gap) or immutable.
  • The 0: zero errors in restore tests — backups only count once recovery is proven.
  • Separate credentials and MFA for the backup infrastructure.
  • Measure recovery time realistically: RTO applies to restoring, not to backing up.

Frequently asked questions about 3-2-1 backup rule

Does the original count towards the three copies?

Yes — three copies means: the production data plus two backups. More important than counting is independence: the copies must not hang off the same storage system or be reachable via the same credentials.

Does a cloud sync like OneDrive or Dropbox count as backup?

No. Synchronisation replicates changes — including encryption by ransomware and accidental deletion. A backup needs independent, versioned copies with their own retention; recycle bin and version features are only a limited stopgap.

Why is 3-2-1 not enough against ransomware?

Because modern attackers deliberately destroy backups first: they compromise admin accounts and delete or encrypt reachable backups before attacking production. Only copies that are logically separated and immutable or offline help against that.

How often should you test recovery?

Regularly and staggered: single files continuously and automated, complete systems at least quarterly, a full disaster restore including order and dependencies at least annually. The 0 in 3-2-1-1-0 means exactly that: proven, error-free restores.

What role does the network play in backup?

A double one: bandwidth and latency determine whether backup windows and recovery times hold — especially for off-site copies. And segmentation protects the backup infrastructure from falling in the attack: its own network segment, its own access, no pass-through from production.

Wondering how this looks in your own network? Talk to KAEMI: we plan, build and manage the right solution with you.