IT infrastructure
Backups you can actually restore: a practical checklist
A backup is only useful if it can be restored in time. How to check yours.
· 1 min read · Neturon

Many organisations find out how good their backups are on the day they need them. A few plain questions, asked now, avoid that.
Decide what "recovered" means
For each important system, agree two things with the people who use it: how much recent work you could afford to lose, and how long you could manage without it. Those answers set how often backups run and how quickly a restore has to happen.
The checklist
- Keep more than one copy, with at least one away from the main site or account.
- Keep at least one copy that ransomware or an accidental deletion cannot change.
- Include cloud services such as email and file storage, not only servers.
- Protect backups with the same care as live data: encryption and limited access.
- Test a restore on a schedule, and write down how long it took.
- Know who is responsible for checking that backup jobs succeeded.
Backups and data protection
Backups contain personal data, so UK GDPR still applies to them. Retention periods should match your records policy, and a restore plan is part of keeping personal data available and secure.
Related service
IT Infrastructure & Technical Support
If this matches a piece of work you are planning, tell us about it and we will suggest a sensible first step.
General guidance only. It is not legal, financial or regulatory advice, and it does not describe the results of any client project.
More insights
Data protection
Building UK GDPR into a business system from the start
The data protection features to specify at the beginning, rather than add later.
AI solutions
Getting ready for AI: start with one task and your data
A practical way to choose a first AI use case, check your data and keep people in control.
Open-source software
Open source, off-the-shelf or custom: choosing with eyes open
How to compare licences, support, ownership and running costs before you choose.
