Mistake: treating a successful backup job as proof that the backup is usable. RESTORE VERIFYONLY checks whether SQL Server can read a backup and validate its integrity without restoring the database. It is a practical validation step, not a substitute for testing full restores. section 12.4.2 section 12.12
Use verification as part of a safer backup routine:
- Create backups with CHECKSUM so verification can validate the backup checksum; expect reduced backup throughput, especially for large databases. section 12.4.2
- Add RESTORE VERIFYONLY as a job step after native backup jobs and monitor whether that step completes successfully. section 12.4.2
- Do not assume verification proves recoverability: corruption can still exist, so use automated restores when infrastructure capacity permits. section 12.4.2
- Coordinate with the backup team when an enterprise tool hides verification across the estate; use its API for a scripted approach. section 12.4.2
Verify the Marketing backup
RESTORE VERIFYONLY FROM DISK = 'D:\Backup\MarketingFull27122023.bak' WITH CHECKSUM;
Listing 12.5 Verifying a backup
RESTORE VERIFYONLY FROM DISK = 'D:\Backup\MarketingFull27122023.bak' WITH CHECKSUM ;
Open the complete verification listing for the executable T-SQL example. section 12.4.2
