Across the businesses we assess, the same pattern comes up again and again: the backup is configured, it reports success, and everyone assumes the job is done. Backing up and restoring are two different tasks, though, and only one of them gets tested by accident. A backup that has never been restored is a promise, not a safety net.

The failures we find are rarely dramatic. A folder that stopped being included when the file server was reorganised. A cloud sync that quietly paused after a password change and never resumed. A database that is being copied while it is open, so the copy is subtly broken and only reveals itself when you try to use it. Each one passes the daily check and fails the only test that matters.

A restore test is not complicated and it does not need special software. You pick a real file, ideally something from a few weeks back, and you ask the backup to give it to you. If it comes back whole and opens correctly, you have learned something true. If it does not, you have learned it on a quiet afternoon rather than during a flood, a theft or a ransomware morning.

For regulated firms this matters twice over, because being able to demonstrate recovery is part of the point, not an extra. A commissioner or auditor will not accept a green light as evidence; they will ask when you last proved it. The honest answer for most people is never, and the good news is that changing that answer takes about twenty minutes.