The 3-2-1 Rule, and Why a Backup Stored With What It Protects Doesn't Count

Backup & Disaster Recovery Basics

Chapter 3 · The 3-2-1 Rule, and Why a Backup Stored With What It Protects Doesn't Count

Chapter 2 covered what's actually inside a backup. This chapter covers where it needs to physically and logically live to be useful in a real disaster — because a huge number of "backups" that technically exist don't actually protect against the specific disasters that matter most, purely because of where they're stored.

The Rule, and What Each Number Actually Protects Against

3 copies

The original plus two backups.

Protects against: any single copy failing or becoming corrupted — redundancy in numbers.

2 media types

Not all copies on the same kind of storage.

Protects against: a failure mode specific to one media type or format — a bad drive batch, a firmware bug, a software issue affecting one backup format.

1 offsite

At least one copy physically or logically separate from the original.

Protects against: whole-site disasters — fire, flood, theft, and (increasingly, the most common reason this matters) ransomware spreading across a local network.

The Central Idea of This Chapter

A backup stored right next to what it protects only guards against one specific kind of disaster: accidentally deleting or corrupting the original while the copy stays untouched. It does nothing against a disaster that reaches both at once — the server itself failing, the building it's in burning down, or ransomware that spreads across the local network and encrypts or deletes everything it can reach, including a backup drive plugged into the very machine it was supposed to protect.

Ransomware makes this the whole point, not a theoretical edge case

Modern ransomware often specifically seeks out and encrypts or deletes connected and network-accessible backups before finishing its attack, precisely because a working backup is what would let an organization refuse to pay a ransom. A backup that ransomware can reach the same way it reached the original data isn't a real safety net — Chapter 8 covers this specific threat, and the defenses against it, in depth.

Does This Actually Count as "Offsite"?

Backup location	Counts as offsite?
An external drive plugged into the same server	No — reachable by anything that reaches the server, including ransomware
A NAS device in the same server room	No — a single fire, flood, or theft takes out both at once
A different room in the same building	Usually no — most building-wide disasters still reach both
A separate building in the same city	Partially — protects against a single-building disaster, not a citywide one
Cloud storage or a genuinely distant physical location	Yes — isolated from local, network-wide, and single-site disasters alike

Worked Example: The Backup That Burned Down With the Server Room

An organization's "backup strategy" turns out to be a nightly copy to a NAS device sitting in the same server room as the primary server. On paper, backups have run successfully every night for years. When an electrical fire damages the server room, the NAS goes with it — years of "successful" backups, and the data they protected, are gone in the same event. Proper 3-2-1 would have kept at least one of those copies somewhere the fire could never reach, regardless of how reliably the nightly job itself had been running.

Why this connects directly to Chapter 1's own central claim

Every one of those nightly backup jobs could report "success" for years, exactly matching Chapter 1's warning that a success status only confirms a copy was made — it says nothing about whether that copy sits somewhere actually safe from the disaster that eventually happens.

Hands-On Exercises

Exercise 1

Explain specifically what disaster each of the three numbers in "3-2-1" protects against, and why a backup satisfying only two of the three still leaves a real gap.

📄 View solution

Exercise 2

Explain why an external drive plugged into the same server it backs up is described as providing no real protection against ransomware specifically.

📄 View solution

Exercise 3

Explain why the NAS-in-the-server-room worked example is described as connecting directly to Chapter 1's own central claim, even though nothing about the backup job itself ever failed.

📄 View solution

Chapter 3 Quick Reference

3 copies — protects against a single copy failing
2 media types — protects against a failure specific to one storage type or format
1 offsite — protects against whole-site disasters, including ransomware spreading across a local network
A backup stored with what it protects only guards against accidental deletion — nothing that takes out both at once
Same building, same room, or a drive plugged into the same machine — none of these count as genuinely offsite
Next: Chapter 4, verifying a backup actually ran — and resolving Chapter 1's own deleted-folder ticket