A backup job that reports success has only proven it wrote a file. Verification proves the file is readable. A test restore proves the file can rebuild your PC. This page does all three, in rising order of honesty.
Image files live on real disks, and real disks develop bad sectors, interrupted writes and quiet corruption. Reflect knows this, which is why it can verify an image - reread it and check its internal checksums - and why disciplined users go one step further and restore it once, on purpose, while nothing is wrong.
Levels 1 and 2 are automatic once set. Level 3 is a habit - once after setup, then after big changes.
During a backup, Reflect writes checksums through the image. Verification reads the whole file back and compares - so a sector that has gone bad on the backup drive, or a file damaged by a failing USB enclosure, is caught now, while the original PC is healthy and a fresh image costs nothing.
What verification cannot promise: that the data inside was worth having, or that your rescue media boots. Those need the other two levels.
Reflect can attach an image as a drive letter inside Windows. Open it, walk into the folders, and copy out one document you care about. This thirty-second test proves the file system inside the image is readable and your data is really in there - not just Windows, but your work.
Once, while everything is calm, do the full drill: boot the rescue media, restore the latest image to a spare or old drive, boot from it. If a spare drive is not available, Reflect's viBoot can start an image as a Hyper-V virtual machine for a quick boot check where that feature is available.
Then make it a rhythm: auto-verify on every backup, a test restore after big changes - a drive swap, a Reflect upgrade, a new backup destination - and at least a couple of times a year in between.
See every click in Macrium Reflect - the image, the settings and the restore - live in the full video.
▶️ Watch Full VideoIt reads the entire image, so the time follows the image size and the backup drive's speed - think of it as similar to copying the file once. That is why it runs automatically after the job rather than being remembered by a human.
Rarely, yes - from things verification does not touch: rescue media that cannot boot, a target drive problem, a wrong boot setting. That small gap is exactly why the test restore exists.
Yes - it costs only background time and it is the earliest warning that a backup destination is going bad. Skipping verification to save minutes is how silent corruption gets a month's head start.