The uncomfortable truth about backups
Many people discover that their backup is broken at the exact moment they need it. The software stopped running months ago, the drive filled up, the wrong folder was selected, or the files are there but cannot be opened. A backup that has never been restored is an assumption. Testing turns the assumption into knowledge.
The good news is that testing does not need to be elaborate. A few minutes a few times a year catch most of the problems.
How backups fail quietly
Knowing the common failure points tells you what to check.
- The job stopped. Software updates, a changed password, a full destination or an unplugged drive can halt a backup without any obvious alert.
- The wrong things are selected. New folders, a new phone or a new work project may sit outside what the backup covers.
- The copy is damaged. Drives and memory cards can develop errors that go unnoticed until you read the data.
- The files are unusable. Encrypted backups can be impossible to open if the password or recovery key is lost.
- The account lapsed. A subscription that expired or a storage allowance that filled up may mean new data is no longer being saved.
- It copies mistakes. If damaged or unwanted changes are mirrored, the good version may already be gone.
Three levels of testing
Think of testing as a ladder. Do the first level often and the others on a schedule.
Level 1: Look at the status
Open your backup program or service and check:
- The date and time of the last successful backup
- Any error or warning messages
- How much space remains at the destination
- Which folders and devices are included
Do this monthly. For phones, check the last backup date in settings. This takes less than five minutes and catches many problems.
Level 2: Restore a few files
Pick several files at random, ideally including a recent one, an old one and a large one. Restore them to a different folder and open each. Do they open? Are they the right version? Is the content complete? Photos should display fully, documents should open without errors, and spreadsheets should show the data.
Do this every few months. Choosing the files yourself, rather than letting the software pick, gives a better view of whether the things you care about are really there. On a cloud service, try downloading a few items through the website, since that tests your sign-in and access path too.
Level 3: Practice a full restore
Once or twice a year, or after changing your setup, rehearse the real thing. You do not need to wipe your computer. Instead:
- Restore a whole important folder to a spare location or a spare drive.
- Compare the file count and spot-check content.
- Time the process, so you know how long a full recovery might take.
- For a computer backup, find out what you would do if the machine itself were gone. Do you have the installation media or instructions, the login information and the encryption password?
This rehearsal reveals gaps no status screen will, such as a missing recovery key, a slow connection or a program that cannot read its own old files.
Special checks for particular setups
Encrypted backups. Confirm you can open them using the password and recovery key you have written down, not the one stored in the machine. Remember the guidance on backup encryption: a lost key can make the data permanently unreadable.
Phones. The only convincing test is seeing the photos and messages from another device or during a restore on a replacement phone. Verify that recent pictures appear in the online library, and check what the chat apps actually saved. See also the steps for phone photo backup.
External drives. Plug them in and open a few files. If the drive is slow, makes odd noises or shows errors, replace it. Drives have limited lives, and a copy on a failing drive is not a real copy.
Cloud services. Check that account recovery works, that your two-step sign-in method is available even without your usual device, and that deleted or old versions are retained as you expect. The point of cloud versus local backup is not just where the copy lives but whether you can reach it.
Ransomware resilience. Check that at least one backup is disconnected or versioned and that older versions exist from before today. The role of backups in ransomware recovery depends on that.
Making testing a habit
People rarely test unless it is scheduled. Tie it to something you already do:
- Put a recurring reminder on your calendar, perhaps quarterly
- Link a status check to the start of each month
- Test after any change, such as a new computer, new phone, new drive or software upgrade
- Keep a short log of the date, what you checked and the result
If you manage a household, a shared task works well: one person checks the family phone backups and another checks the drive.
What to do when a test fails
A failed test is a success, because you found out in time. Respond calmly:
- Stop and note the problem. Do not delete anything while you investigate.
- Make a fresh copy right away of the most important files by any method available.
- Fix the cause: replace the drive, free up space, fix the credentials or adjust what is selected.
- Run another test to confirm the fix worked.
Keep expectations realistic. Even a well-tested backup does not guarantee future results, since storage can still fail between tests. That is why the 3-2-1 backup rule, with several copies on different kinds of storage, is paired with regular testing rather than replaced by it.