United Kingdom version. Written for the UK: the three-two-one rule, testing restores rather than assuming them, UK GDPR storage limitation, transfer considerations, and NCSC ransomware guidance. US version
Backup Strategy Checklist (UK)
Three copies, two media, one off site, and a restore you have actually tested. For business data, add a retention period and a transfer check.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Backup Checklist?
The rule worth internalising is three-two-one: three copies of anything you cannot lose, on two different kinds of media, with one copy off site. A single external drive in the same room as the computer is one hazard away from being no backup at all, and cloud sync alone is not a backup because it propagates deletions and encryption.
The step everyone skips is the restore. A backup you have never restored from is a hypothesis, and the most common discovery is that the backup was running but excluding a folder, or that the restore requires a password nobody recorded. Testing a restore of a few real files quarterly is the whole difference between a backup and a belief.
For business or personal data about other people, UK GDPR adds a duty that cuts against hoarding: storage limitation means keeping personal data only as long as necessary, so an indefinite backup of everything is both a compliance problem and a bigger breach when it leaks.
- Built on three-two-one with cloud sync treated separately
- Follows NCSC guidance on isolating backups from ransomware
- Covers UK GDPR storage limitation against legal retention duties
- Includes transfer considerations and processor contracts for providers
- Tick, reword and delete items, then export as a Google Form, PDF, CSV or Markdown
Updated
How to use the Backup Checklist
- Build three copies on two kinds of media with one off site, and treat cloud sync as not a backup.
- Keep an isolated or immutable copy, since ransomware targets reachable backups first.
- Enable versioning so a corrupted or encrypted file does not overwrite the good copy.
- Test a restore of real files quarterly, including the password or key needed to do it.
- For business data, set a retention schedule, check where the provider stores data, and have a processor contract.
Worked examples
One external drive beside the computer
Input
Three-two-one section, Essentials only
Output
Off-site copy added
A single drive in the same room shares every hazard with the original, so a fire, flood or theft takes both and leaves no backup at all.
Relying on cloud sync
Input
Versioning items
Output
Versioned backup added alongside sync
Sync propagates deletions and encryption, so without version history an infected file overwrites the good one everywhere it syncs.
Backup never restored from
Input
Restore items
Output
Quarterly restore test established
The usual discoveries are an excluded folder or a missing decryption password, both of which only surface during a restore attempt.
Encryption key in a manager on the backed-up machine
Input
Key items
Output
Recovery kit stored separately and physically
A key that exists only on the device being backed up is unavailable at exactly the moment the backup is needed.
Background and insight
Ransomware changes backup design, and the NCSC is explicit that backups must be isolated from the systems they protect, because attackers target backups first. That means offline or immutable copies rather than a network drive the ransomware can reach, and credentials for the backup system that are not the same as the ones used daily.
Versioning matters as much as copying: an infected or corrupted file that syncs to the cloud overwrites the good version unless history exists, so a backup with thirty days of versions is far more useful than a mirror. The same applies to accidental deletion, which is a more common loss than any attack.
For UK business data, transfers out of the UK engage their own requirements, so where a backup provider stores data matters: an appropriate transfer mechanism and an assessment are needed unless the destination has UK adequacy. A processor contract with the backup provider is also required rather than optional.
Encryption at rest and in transit is the other control, with the practical point that the encryption key or recovery kit must exist somewhere other than the device being backed up. People encrypt backups and store the key in a password manager that lives only on the encrypted machine, which fails exactly when needed.
What to back up is usually underestimated: documents and photographs are obvious, but authenticator seeds, password manager vaults, software licences, browser bookmarks and saved logins, email if it is only on a device, and the configuration that took hours to set up all matter. For businesses, add anything regulated, accounting records and contracts.
Retention for tax and legal purposes pulls the other way from storage limitation, and the resolution is a schedule rather than a default: keep what the law requires for the period it requires, keep nothing personal beyond its purpose, and document the reasoning so an auditor or regulator can see it.
Finally, the human factor: a backup that requires someone to remember is a backup that stops. Automate it, alert on failure to a person rather than a log, and check the alert actually works by breaking it deliberately once.
Common use cases
A first real backup
Three-two-one and what sync does not do.
Ransomware resilience
Isolated and immutable copies.
Business data
Retention, transfers and processor contracts.
Proving it works
The restore test and the alert that fires.
Tips and limitations
- Cloud sync is not a backup. It propagates deletions.
- A backup you have never restored from is a hypothesis.
- Keep one copy offline or immutable; ransomware targets backups first.
- Store the encryption key somewhere other than the encrypted machine.
- Back up authenticator seeds and password vaults, not just documents.
Sources and further reading
- National Cyber Security Centre, National Cyber Security Centre. Backup isolation, ransomware guidance and resilience
- Device security guidance, National Cyber Security Centre. Encryption and device configuration
- Data protection and your business, UK Government. Storage limitation, retention and processor contracts
- Data protection, UK Government. UK GDPR principles including storage limitation
Frequently asked questions
What is the three-two-one rule?
Three copies of data you cannot lose, on two different kinds of media, with one copy off site. A single external drive next to the computer shares every hazard with the original, which is why it does not count as a backup.
Is cloud sync a backup?
No. Sync propagates deletions and encryption to every copy, so a corrupted or ransomware-encrypted file overwrites the good version. Version history or a separate versioned backup is what makes recovery possible.
Why does ransomware change backup design?
Because attackers target backups first, so NCSC guidance is to keep copies isolated from the systems they protect: offline or immutable, with credentials that differ from the ones used for daily administration.
How do I know my backup works?
By restoring from it. Test a restore of real files quarterly, including locating the password or key required, since the usual discoveries are an excluded folder or missing credentials rather than a failed job.
Does UK data protection law affect backups?
Yes. Storage limitation means keeping personal data only as long as necessary, so indefinite backups of everything are both a compliance problem and a larger breach if leaked. A documented retention schedule resolves it against legal retention duties.
What do people forget to back up?
Authenticator app seeds, password manager vaults, software licences, email held only on a device, browser saved logins, and configuration that took hours to build. Documents and photographs are the part people remember.
Is there an in-depth guide to the Backup Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.