Backup verification

Backup consoles report success when the job ends, which says nothing about whether a file can be pulled back, so the real test tends to happen on the worst possible day. This workflow turns verification into a scheduled job that touches every protected system on a rotation. It restores a known file from the newest recovery point into an isolated area, checks that it opens and matches what the source system says it should contain, and on a slower cycle restores a whole representative server for each tier. It also opens the break-glass credentials a real recovery would depend on, and times every step separately, so the recorded recovery time is built from measurements instead of copied from a target. A job that passes on the console but fails on restore raises a ticket against the backup owner the same day, and a system with no passing result in ninety days is called out by name in the coverage report. A human still chooses the representative systems, signs off on the measured times, and decides which gaps are acceptable before an audit.