To verify a backup on Windows, do three things: check the backup log says it completed without errors, compare the backup against your files (size, file count and a few spot checks), and restore a sample of files to a different folder and open them. For a system image, also mount it or browse it, and test that your rescue USB or recovery drive actually boots your PC. A backup you have never restored from is a hope, not a plan.
Here is how to do each check, how often, and what automatic verification does and does not prove.
Why backups fail without you knowing
Backups rarely fail loudly. Common silent failures include:
- The schedule stopped after a Windows update or a password change.
- A new folder you created was never added to the backup.
- Open or locked files were skipped every night.
- The backup drive developed bad sectors, so some files cannot be read back.
- The backup is encrypted and the password is lost.
- The rescue USB was made for an older PC, or will not boot with current firmware settings.
Each check below catches a different one of these.
Check 1: read the log and the last backup date
Start with the easy part: did the backup run, and did it report errors?
| Tool | Where to check |
|---|---|
| File History | Control Panel → File History shows when files were last copied |
| Backup and Restore (Windows 7) | Control Panel → Backup and Restore (Windows 7) shows the last backup and its result |
| wbadmin or Task Scheduler jobs | wbadmin get versions, the task's Last Run Result, and Event Viewer |
| Robocopy scripts | The log file written with /LOG:; look at the summary table's Failed column |
| Backup programs | The job history or log screen |
Look for warnings as well as errors. "Completed with warnings" often means some files were skipped. If the last backup is older than you expected, see scheduled backup not running in Windows.
Check 2: compare the backup with your files
- In File Explorer, right-click an important folder, such as Documents, and choose Properties. Note the size and the number of files and folders.
- Do the same for that folder in the backup, or check the size your backup program reports.
- The numbers should be close. Small differences are normal if you have excluded temporary files; large gaps mean something is missing.
- Check that folders you added recently, and folders outside your user profile such as
D:\Work, are included.
For a stricter check, you can compare a file's hash before and after. In PowerShell, run Get-FileHash "C:\Users\You\Documents\report.xlsx" and the same on the restored copy. Matching hashes mean the files are identical.
Check 3: test-restore some files
This is the check that matters most.
- Pick five to ten files of different types: a document, a spreadsheet, a photo, a video, an email data file, and something old.
- Restore them to a new folder, such as
C:\RestoreTest, not over the originals. - Open each one in its program. A file that restores but will not open is not backed up.
- Restore an older version of one file, to confirm version history works.
- If your backup is encrypted, do this at least once using the password from where you store it, not from memory.
- Delete the test folder afterwards.
Do at least one test restore on a different PC. If your computer is stolen or destroyed, that is exactly the situation you will be in, and it reveals missing passwords or software you did not know you depended on.
Check 4: verify a system image
You do not need to wipe your drive to test an image.
- Browse it. A Windows system image is stored as .vhdx files in the
WindowsImageBackupfolder. In Disk Management, choose Action → Attach VHD, tick Read-only, and check the drive that appears contains your Windows and user folders. Detach it when done. - Check its size and date. The image should be close to the used space on the drive it covers.
- Test a full restore on spare hardware if you have it, such as an old drive in the same PC. This is the only complete proof, and worth doing once for a business PC.
Check 5: test your rescue USB
- Plug in the rescue USB or Windows recovery drive and restart.
- Open the boot menu (often F12, F11, Esc or F8, depending on the manufacturer) and choose the USB.
- Confirm it starts, sees your internal drive, and sees your backup drive or network location.
- Restart and remove it without restoring anything.
If it does not boot, check Secure Boot and boot order in the firmware settings, or recreate it. Our guide to creating a bootable rescue USB covers this.
What automatic verification does
Many backup tools offer a "verify" option. Typically this reads the backup back after writing it and checks it against checksums or the source, confirming the data was written correctly and can be read. That catches bad sectors, interrupted writes and storage problems, which is valuable, especially for backups nobody looks at.
What it cannot prove is that you backed up the right things, that you know the password, or that the restore process works in a real emergency. Automatic verification plus occasional test restores covers both sides.
Rocket Backups checks every backup after it runs, shows its status in the tray icon, and emails you if a job fails, a drive is missing or space runs low. Test restores are quick: pick a date on the timeline, browse or search for a file, and restore it somewhere new. You can also open a system image as a drive letter to browse it without restoring. Rocket Backups makes regular checks easy, but the monthly test restore is still worth doing.
A simple testing schedule
| How often | What to check |
|---|---|
| Every backup | Automatic verification and failure alerts |
| Weekly | Glance at the last successful backup date |
| Monthly | Restore a handful of files and open them |
| Twice a year | Browse a system image, boot the rescue USB, restore on another PC |
| After any change | New PC, new drive, new important folder: run a full check |
Put it on your calendar. Testing is the item most people skip on their computer backup checklist, and it is the one that tells you whether the rest of the list worked.
Frequently asked questions
How often should I test my backups?
Restore a few files every month and do a bigger test, such as booting the rescue USB or browsing a system image, a couple of times a year.
What does backup verification check?
Verification reads back the backup and checks it against checksums or the source, confirming the data was written correctly and can be read.
Is a successful backup log enough?
It is a good sign, but only a test restore proves you can actually get files back. Do both.
