Neither the UK GDPR nor the NCSC's backup guidance gives a number of days for how long to keep backups. Set the period by asking how far back you might need to go to recover cleanly, add a margin for how long damage could go unnoticed, then check the result against what you must keep (company and VAT records are generally six years, but those duties attach to the records, not to every backup) and what you should not keep longer than you can justify (personal data). NCSC's own illustration is daily restore points for a month and monthly ones for a year. Treat that as a starting shape, not a rule.
Start with recovery, then test against your obligations
Choose backup retention in that order: how far back might we need to go, and only then what are we required or allowed to keep. Most people do it the other way round, grab a number that sounds compliant and live with the consequences.
A retention period is simply how long a restore point is kept before it is allowed to expire. It is a different decision from how often you back up. Frequency decides how much recent work you could lose. Retention decides how far back in time you can reach.
The ICO says the UK GDPR does not dictate how long you should keep personal data and that you must be able to justify your own periods. NCSC's guidance on ransomware-resistant backups likewise gives no mandatory duration and leaves it to the system owner's risk appetite. So the number is yours to set and yours to explain. Keeping everything for seven years just in case is less a policy than a hoard.
Backups are for recovery, not for your records archive
Record-keeping law does set periods. GOV.UK says a limited company must keep its accounting records for 6 years from the end of the last company financial year they relate to, and that period gets longer if a transaction spans more than one accounting period, the Company Tax Return was sent late or HMRC has started a compliance check. For VAT, HMRC's notice says that generally you must keep business records for VAT purposes for at least 6 years, and that records used for other tax purposes may need to be kept for longer.
It is easy to read that as 'keep every backup for six years'. It does not say that. Those duties attach to the records themselves. Our view is that the records belong somewhere designed for them - your accounting package, your document store or a deliberate export - with the backups acting as the safety net for that system.
A daily backup chain stretched over six years is an awkward archive. Finding one invoice means restoring a whole point-in-time system, and every personal detail in it stays alive for the full period. If an accountant or auditor says something must be kept for longer than your backups run, the useful follow-up question is where that record will live and who can find it. The answer should be somewhere searchable, not 'in the oldest tape'.
Work out how far back you would need to go
For each group of data, ask how long it would take someone to notice that something had gone wrong. Your retention needs to be longer than that, with margin for holidays and quiet months. Four situations tend to set the answer.
- Accidental deletion or overwrite: usually spotted quickly, but sometimes only when someone needs the file at month-end or year-end.
- Silent corruption: a bad import, a failing disk or a faulty sync can damage data gradually. You need a restore point from before the damage began, and you only find out when someone opens the affected record.
- Ransomware or another intrusion: NCSC's principles say a sensible retention policy lets you go back to a backup from before the attack took place. The compromise may predate the day you noticed it, so the newest restore points are not guaranteed to be clean.
- Periodic needs: year-end figures, quarterly reporting or seasonal systems that are untouched for months and then suddenly essential.
An illustrative schedule for a small firm
To make this concrete, picture a fictional 25-person professional services firm. These figures are placeholders to show the reasoning, not a recommendation for your business. They echo the example NCSC uses (daily backups for a month, monthly backups for a year), which NCSC offers as an illustration and not as a prescribed duration.
- Shared files and the main line-of-business database: daily restore points for 30 days, monthly ones for 12 months. This only works if the team would normally spot a missing or damaged file within a few weeks, and the monthly tier covers problems found after month-end.
- Accounting data: the same recovery schedule. The six-year record duty is met by keeping the records and year-end reports in the accounting system or a records store, confirmed with the firm's accountant, rather than by lengthening the backup chain.
- Old project folders nobody has opened for years: move them to an archive with its own deliberate retention decision, instead of carrying them through every daily backup.
Check the number against data protection rules
The UK GDPR principle of storage limitation means you should not keep personal data longer than you need it. The ICO says you should not hold it indefinitely just in case, and that when you delete personal data from a system you should also delete it from any backup of that system. Backups are not outside the rule.
In practice that is rarely instant. For erasure requests, the ICO accepts that live data may be erased straight away while backup copies stay until they are overwritten, provided you put the backup data beyond use, do not use it for any other purpose, keep it only until it is replaced under an established schedule and are clear with the individual about what happens. A fixed, documented expiry makes that sentence easy to write: it leaves our backups within a known number of days. A six-year chain makes the same sentence uncomfortable.
Our reading of 'beyond use' is practical: if you ever restore from a backup taken before a deletion, re-apply that deletion before the data goes back into live use. Keeping a simple record of erasure requests for as long as your oldest backup lives makes that possible.
One caution on currency: the ICO storage limitation and erasure pages currently carry a notice that the guidance is under review following the Data (Use and Access) Act and may change. Re-read them when you review your schedule rather than treating today's wording as permanent.
Make retention hold up when someone hostile has an admin account
A retention schedule that a stolen administrator account can shorten in one click is a wish, not a control. NCSC's principles for ransomware-resistant backups give some usable direction here, and they apply to on-premises and cloud backups alike.
- Keep by time period, not by number of backups. NCSC recommends storing backup data for a fixed period rather than a fixed count, because a count-based scheme lets a burst of new backups push older good ones out.
- Make early deletion hard. NCSC describes soft delete, where a deletion request leaves data recoverable for a retention period, and write-once storage as ways to stop backups being deleted or altered. Check what your own product calls and supports these.
- Be able to restore from an earlier version even if later ones are corrupted, and keep at least one backup disconnected from the network, which NCSC calls the offline rule.
- Do not mistake built-in cloud recovery for a retention plan. Microsoft's documentation describes version history, recycle bins and a OneDrive restore to any point in the previous 30 days. These are useful, but they are time-limited recovery features. If your answer to the recovery question is 12 months, they do not cover it on their own.
A safe way to assess your own retention
This is a paper exercise followed by one controlled restore. Nothing here changes live data until you decide to change a schedule, and you should make any change to a retention setting on a pilot job first, because shortening retention permanently discards older restore points once they expire.
- List your data groups, starting with the data the business could not operate without. Shared files, the accounting system, email and any line-of-business database are the usual candidates.
- For each group, write down how long it would realistically take to notice damage, including holidays and month-end. Add a margin. That is your minimum recovery retention.
- Note what else applies: statutory records and where they actually live, contract terms, any backup requirements in an insurance policy or customer agreement, and whether the data contains personal information. Ask your accountant about record periods rather than guessing.
- Choose a period per group and set it as a time period, not a count. Add a longer monthly or yearly tier only where you can state the reason in a sentence. If the reason is 'just in case', leave it out.
- After one full cycle, open your backup console or job reports and confirm the oldest restore point that should have expired has gone and the oldest one that should remain is still there. This is a read-only check.
- Restore a file or folder from the oldest retained point to a separate location, never over live data, and open it. NCSC advises learning to restore before you need to and checking the backup contains your important data. A file that opens is your success check.
- Record the result on one page: data group, retention period, reason, owner and next review date. Review it when systems change, after any incident and when ICO guidance is updated.
When to take advice before changing anything
This is engineering guidance, not legal advice. Take qualified advice first if you work in a regulated sector, a contract or insurer specifies backup or retention terms, or you know of a dispute, complaint or regulator enquiry. In those cases, do not shorten retention or let relevant restore points expire until someone qualified has said it is safe.
Technical terms explained
- restore point
- A saved version of your data from a particular moment that you can recover to.
- retention period
- How long a backup or restore point is kept before it is allowed to expire and be deleted. It is separate from how often backups are taken.
- soft delete
- A safeguard where a deletion request does not remove data straight away. It stays recoverable for a set period, which helps if the request was malicious or mistaken.
- storage limitation
- A UK GDPR principle: personal data should be kept no longer than needed for the purpose it was collected for, and you must be able to justify the period.
Sources and further reading
- NCSC - Principles for ransomware-resistant on-premises backups
- NCSC - Principles for ransomware-resistant cloud backups
- NCSC - Offline backups in an online world
- NCSC - Small organisations guide: backing up your data
- ICO - Principle (e): Storage limitation
- ICO - Right to erasure
- GOV.UK - Company and accounting records
- GOV.UK - Record keeping (VAT Notice 700/21)
- Microsoft Learn - Cloud data security measures in SharePoint and OneDrive