Our maintenance scripts run RESTORE VERIFYONLY WITH CHECKSUM after each database is backed up to our backup server. A few of the databases often fail with the error shown below. But if we re-run the exact same verify command manually later, it runs without a problem and says the file is valid.

Msg 3203, Level 16, State 1, Server SQL11, Line 1
Read on "\\\Backup\DBName\FULL\DBName_FULL_20160214.bak" failed: 13(The data is invalid.)
Msg 3013, Level 16, State 1, Server SQL11, Line 1
VERIFY DATABASE is terminating abnormally.

Why does VERIFYONLY fail when the maintenance plan is running but not when we run it manually?

  • Have you tried copying the backup locally and then run the restore verifyonly ? – Kin Shah Feb 17 '16 at 17:16
  • Network blips due to a flaky / unstable / overwhelmed network perhaps. Copy locally like @Kin suggests before running the commands against the local copy, and I bet the problem disappears. – Aaron Bertrand Feb 17 '16 at 17:27
  • Kin, it works fine when I run the verify manually, even if the backup file is still on the network drive. I don't want to copy the backup file around as part of the maintenance job, because that will make it more complicated and slower. I'll look into network issues. – Josh Yeager Feb 17 '16 at 18:55
  • Is CHECKSUM necessary? – Peter Feb 23 '16 at 22:34
  • Maybe not. We added CHECKSUM as an extra verification. Why? – Josh Yeager Feb 24 '16 at 2:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.