Backup shows as completed successfully but actually failed
Andrew Hodge
Posts: 132
Hi,
SQL Backup v5.2.0.2825
I have a backup which has an outcome of successful in the Activity monitor but actually failed with the the following message
Thread 0 error:
EOF#2 validation failed. Device 0. Expected 72, available 38
Thread 1 error:
EOF#2 validation failed. Device 0. Expected 72, available 38
Thread 2 error:
EOF#2 validation failed. Device 0. Expected 72, available 38
Validation of all backup files failed
SQL error 3013: Verify database is terminating abnormally
SQL error 3203: Read on 'SQLBACKUP_464B82E8-6CCB-4296-BEF4-B03133F5A4D01' Failed, status = 995.
SQL backup emailed me that the verify had failed. This was for the msdb database and appears to be a one off.
Why does the outcome in activity history on the GUI show as successful if it failed?
SQL Backup v5.2.0.2825
I have a backup which has an outcome of successful in the Activity monitor but actually failed with the the following message
Thread 0 error:
EOF#2 validation failed. Device 0. Expected 72, available 38
Thread 1 error:
EOF#2 validation failed. Device 0. Expected 72, available 38
Thread 2 error:
EOF#2 validation failed. Device 0. Expected 72, available 38
Validation of all backup files failed
SQL error 3013: Verify database is terminating abnormally
SQL error 3203: Read on 'SQLBACKUP_464B82E8-6CCB-4296-BEF4-B03133F5A4D01' Failed, status = 995.
SQL backup emailed me that the verify had failed. This was for the msdb database and appears to be a one off.
Why does the outcome in activity history on the GUI show as successful if it failed?
Comments
1 - when an integrated verification fails, the related backup is flagged as successful. In the next update, the backup will now be flagged with an error.
2 - integrated verification sometimes fails, even if the backup file is valid.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8