The 3-2-1 backup rule, and how to actually do it in 2026
Key takeaways
- The 3-2-1 backup rule is three copies of your data, on two different types of media, with one copy held offsite
- The NCSC points out that 3-2-1 does not require any copy to be offline, and ransomware has encrypted connected drives and cloud backups alike
- 3-2-1-1-0, a variant from Veeam, adds one immutable copy and zero recovery errors
- Versioning matters more than raw capacity, because you need a copy from before the thing you are recovering from happened
- A backup you have never restored from is a theory, so test restores regularly
Part of our Backup and recovery guide. See all guides.
This article contains affiliate links. We may earn a small commission at no extra cost to you. Details
Plug an external drive into a laptop, drag your files across, leave it plugged in. That is not a safe backup. Ransomware treats it as a second target, because anything your computer can write to, malware running on your computer can encrypt.
The NCSC says it has seen numerous incidents where ransomware encrypted not only the original data but also the connected USB and network storage drives holding the backups, and in some cases connected cloud storage too.
What the 3-2-1 backup rule actually means
Three numbers, one sentence each.
- Three copies of your data. The live copy you work on, plus two backups. Not one. Two.
- Two different types of media. A drive plus a network share, or a drive plus cloud storage, is two.
- One copy offsite. Somewhere a flood, a fire or a burglary at your address cannot reach. Cloud counts. So does a drive kept at another site, if you actually rotate it.
The NCSC describes 3-2-1 as the most common method for creating resilient backups, and says it is popular because it scales well, including using the cloud for the offsite copy. TechTarget says the method leaves no single point of failure: an organisation is covered if one copy is corrupted or a technology fails, and also if a natural disaster or theft wipes out the physical storage.
Is the 3-2-1 backup rule outdated?
No, but it was written for fires and failed disks, not for an attacker who hunts for backups. The NCSC's own wording is the clearest statement of the gap: 3-2-1 "does not require any backup location to be offline".
The fix is not to throw the rule away. It is to add a copy that cannot be changed from your network:
- Offline. The NCSC's first rule for backups is to keep at least one offline at any given time, so an incident cannot affect all of them simultaneously. For a drive, that means unplugged. For cloud storage, which you cannot unplug, it means backup clients hold no valid credentials while the storage is not in use, and the storage denies connections while it is cold.
- Immutable. Storage where the backup software can add new data but cannot overwrite or delete existing backups. The NCSC says that if ransomware is acting with privilege only to create new data, it cannot overwrite your existing backups, and compares this to traditional write-once storage, but cheaper and more scalable.
3-2-1-1-0 and other variants
Several extended versions of the rule exist.
- 3-2-1-1-0. Veeam says it extended the rule to 3-2-1-1-0, which adds one immutable copy and results in zero recovery errors. Veeam says an immutable or air-gapped copy is essential because ransomware increasingly targets backups, and if your only protection is connected to your network, it can be compromised.
- 4-3-2. TechTarget describes this as four copies of data in three different locations, two of them offsite.
- 3-2-1-1. TechTarget also lists 3-2-1-1 as another variation.
3-2-1 backup rule examples
A home or sole trader
- Copy one: the laptop itself.
- Copy two: an external drive, connected for the backup and then unplugged. An always-attached drive is inside the blast radius.
- Copy three: a cloud backup service that keeps previous versions of files, with multi-factor authentication on the account.
Unplugging the drive is what makes it the offline copy the NCSC asks for.
A small business
- Copy one: the live data on laptops, a file server or cloud apps.
- Copy two: a NAS on site, such as the Synology DS224+, with snapshots that a client machine cannot overwrite.
- Copy three: cloud storage set so only the backup job can add data and nothing can delete it until the retention period ends.
Keep the number of devices with backup credentials to a minimum. The NCSC says standard user devices should not be able to modify cloud backups directly. Our backup storage calculator works out how much capacity the NAS and cloud copies need for a given retention policy.
A larger organisation
- Copy one: production systems.
- Copy two: backups to on-site storage for fast operational recoveries. TechTarget advises keeping this copy on separate equipment from the original system.
- Copy three: a replicated or cloud copy at another site, with immutability switched on.
- The extra 1: an immutable or offline copy managed under separate credentials, so one stolen admin account cannot reach every copy. The NCSC's principles for cloud backup services say destructive requests, such as deleting backups, should be authorised out of band.
- The 0: scheduled restore tests and alerts on backup jobs.
Why versioning beats capacity
Ransomware encrypts files where they sit. A backup that only mirrors the current state of your files can copy the encrypted versions over the good ones.
Versioning is what saves you. You do not need the current state of your files, you need the state from before the thing happened. The NCSC advises setting retention by time rather than a fixed number of backups, so an attacker cannot push out the good copies by writing a series of corrupted ones in quick succession. Its example is daily backups kept for a month and monthly backups kept for a year.
Test the restore, or you do not have a backup
The NCSC says backups should be made regularly and tested regularly to check they work as expected. For cloud backups it suggests tests that can run on demand, without disrupting live systems, so you can spot a backup that has been corrupted. A simple test is to restore a folder or a server somewhere else and open the files.
The NCSC also warns that if an encryption key is deleted or changed, an attacker does not need to touch the backup at all, so keys should be protected to make sure backup data can be decrypted when necessary.
The bit people forget
Backups protect data. They do not protect accounts. If someone talks their way into your identity provider, as in the vishing calls that got into Abbott, a perfect 3-2-1 setup does nothing, because the attacker is authorised. The NCSC says every user able to access cloud backups should be protected in line with its password and multi-factor authentication guidance.
Backups sit alongside patching and access control rather than replacing either. Keeping current with fixes like August's Patch Tuesday zero-day helps stop attackers getting in through known vulnerabilities. The backup is what stands up when all of that fails anyway.
What the NCSC, the ICO and UK law say
The NCSC calls 3-2-1 the most common method for creating resilient backups, and adds its own rule on top: keep at least one backup offline at any given time, because 3-2-1 by itself does not require any copy to be offline.
The ICO points to the same NCSC advice. Its ransomware guidance says measures such as offline backups, or those in the NCSC's Offline backups in an online world blog, are important to make sure you can restore personal data. The ICO's guide to data security says the UK GDPR security principle requires measures that let you restore access and availability to personal data in a timely manner after a physical or technical incident, and its checklist includes an appropriate backup process and basic controls such as those in Cyber Essentials.
UK law. UK GDPR Article 32, applied by the Data Protection Act 2018, puts that into law: appropriate technical and organisational measures, including the ability to restore the availability of and access to personal data in a timely manner, and a process for regularly testing, assessing and evaluating how effective those measures are. For personal data, the offsite and offline copies are a legal duty as well as good practice.
Frequently asked questions
What is the 3-2-1 backup rule?
Keep at least three copies of your data, on two different types of media, with one copy offsite. The NCSC calls it the most common method for creating resilient backups.
Is the 3-2-1 backup rule outdated?
No, but it is incomplete. The NCSC notes that 3-2-1 does not require any backup to be offline, and ransomware has encrypted connected USB drives, network storage and cloud backups. Add an offline or immutable copy.
What is the 3-2-1-1-0 backup rule?
A variant from Veeam that adds one immutable copy to 3-2-1 and results in zero recovery errors.
Does cloud storage count as the offsite copy?
Yes. The NCSC says cloud storage guarantees physical separation from your live environment, but it also needs to be digitally disconnected when not in use, with backup clients holding no valid credentials in between.
How long should backups be kept?
Set retention by time, not by a fixed number of copies, so a burst of corrupted backups cannot push out the good ones. The NCSC gives the example of daily backups kept for a month and monthly backups kept for a year.
Some links in this article are affiliate links. We may earn a small commission at no extra cost to you.
Does the 3-2-1 backup rule work?
Yes, as a starting point. The NCSC calls it the most common method for creating resilient backups, but notes it does not require any copy to be offline. Add an offline or immutable copy and test the restore.
How can you check if a backup was successful?
Restore from it. A completed backup job only shows that a copy was written. Restoring files from the backup to a separate system shows the copy can be read back, which is the test that matters.
Sources
- NCSC, Offline backups in an online world
- NCSC, Principles for ransomware-resistant cloud backups
- NCSC, Mitigating malware and ransomware attacks
- Veeam, The 3-2-1 backup rule
- TechTarget, 3-2-1 backup strategy
- ICO, Ransomware and data protection compliance
- legislation.gov.uk, UK GDPR Article 32, Security of processing