Read 3-2-1 as Failure Domains
Explain 3-2-1 as a way to avoid shared failure domains.
The reframe: count failure domains, not icons. A team can say "we have three copies" and still be exposed if all three copies are reachable by the same bad event. The 3-2-1 rule pushes you to separate the copies: the working data, another local or device-level copy, and an offsite copy. That separation protects against different classes of loss: hardware failure, accidental deletion, local disaster, account lockout, or malware. The mechanism The rule works by reducing shared fate. A laptop and a drive that is always plugged into it share power, malware, and user-error risk. A cloud sync folder and…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in