SQL Backup Restore Errors (End of File)
DBNewbie_2007
Posts: 47 Bronze 3
It appears all of the backups on our production (aka Prod) and development (aka Dev) servers are bad. While the logs indicate everything backed up fine, when we try to restore the backups we get the following type of message:
Read on "SQLBACKUP_74CDAB93-F01F-4E52-A4DA-12CD419EC4CA02" failed: 38(Reached the end of the file.)
• Tried to do a backup to a different disk, then restore. Still receive the same issue.
• On the one server where backups appear to be OK (using a T_SQL "RESTORE VERIFYONLY FROM DISK" command), the server properties "SQL Backup version" and "Service application version" (10.0.14.1166) all match the RedGate.SQLBackup.UI.exe version.
• On the two servers where the backups receive a "end of file" error, the listed versions are also 10.0.14.1166 (Prod)/10.0.9.1120 (Dev) but the RedGate.SQLBackup.UI.exe version is newer, 10.1.18.2060 (Prod)/10.0.14.1166 (Dev).
• We do know the backups from back in April (Prod) were all good, as we sync our production server with our data warehouse server quarterly.
We also have the Backup Option "CHECKSUM" selected, but not "VERIFY"... would "best practices" be to have this option set? If yes, what is the "hit" in terms of processing speed? A lot of our databases are either hundreds of GBs and a few are TB in size.
Unfortunately, we also just discovered out SQL Pro licenses "Support and Upgrade" contracts had expired.
I also found an older copy of SQLBackup_10.0.14.1166.exe but there does not appear to be a way to "downgrade" the latest installed version in Production.
Read on "SQLBACKUP_74CDAB93-F01F-4E52-A4DA-12CD419EC4CA02" failed: 38(Reached the end of the file.)
• Tried to do a backup to a different disk, then restore. Still receive the same issue.
• On the one server where backups appear to be OK (using a T_SQL "RESTORE VERIFYONLY FROM DISK" command), the server properties "SQL Backup version" and "Service application version" (10.0.14.1166) all match the RedGate.SQLBackup.UI.exe version.
• On the two servers where the backups receive a "end of file" error, the listed versions are also 10.0.14.1166 (Prod)/10.0.9.1120 (Dev) but the RedGate.SQLBackup.UI.exe version is newer, 10.1.18.2060 (Prod)/10.0.14.1166 (Dev).
• We do know the backups from back in April (Prod) were all good, as we sync our production server with our data warehouse server quarterly.
We also have the Backup Option "CHECKSUM" selected, but not "VERIFY"... would "best practices" be to have this option set? If yes, what is the "hit" in terms of processing speed? A lot of our databases are either hundreds of GBs and a few are TB in size.
Unfortunately, we also just discovered out SQL Pro licenses "Support and Upgrade" contracts had expired.
I also found an older copy of SQLBackup_10.0.14.1166.exe but there does not appear to be a way to "downgrade" the latest installed version in Production.
Tagged:
Comments
Removed the GUI component, re-installed the 10.0.14.1166 version and backups appear to be working correctly. Manually ran a "RESTORE VERIFYONLY" on a few files to confirm they were OK.