February 23, 2011 at 3:51 pm
We received a backup file from a client for a SQL2008 R2 database. The file arrived on a USB drive. We are restoring to the same version/build of SQL Server as the backup came from. We successfully copied the file to a local drive and proceeded to run RESTORE VERIFYONLY. This returned the following error:
Msg 3203, Level 16, State 1, Line 1
Read on "g:\dbname_backup_2011_02_20_030001_0977765.bak" failed: (The data is invalid)
Msg 3013, Level 16, State 1, Line 1
VERIFY DATABASE is terminating abnormally.
We have tried to restore (and verifyonly) from the USB drive as well as copy to multiple local drives on different servers, always with the same error. When using FILELISTONLY and HEADERONLY, the backup info is returned successfully.
Our client states that they did not have this issue with the same file on the same USB drive.
We have tried to restore with CONTINUE_AFTER_ERROR with the same error resulting.
It would appear that the backup file is corrupt, however, the client does not seem to agree.
There is limited information about the '13(The data is invalid)' error on the web as it relates to SQL Restores.
Any ideas what this could be indicating?
Thanks!!
TW
February 24, 2011 at 12:59 am
It seems the back file is corrupt. In fact, CONTINUE_AFTER_ERROR is intended to allow to restore after an incorrect page restore - not to allow restore from invalid data.
By the way, have you tried to use RESTORE VERIFYONLY. This command verifies the backup but does not restore it, and checks to see that the backup set is complete and the entire backup is readable.
February 24, 2011 at 7:56 am
Yes, we've tried VERIFYONLY and we get the same error message. If the client was unable to restore the database I'd definitely believe the file is corrupted - however they say they are able to restore from the same drive/backup file that we were unable to. I don't know what to believe at this point. This is the 2nd backup file on a second usb drive that we've experienced this.
TW
February 24, 2011 at 4:32 pm
Are you sure you are both running SQL Server 2008 R2? (Not one of you running SQL Server 2008 SP2?) It seems simple but a lot of people get them confused.
February 24, 2011 at 6:08 pm
Perhaps the drive got damaged during transit? Could try generating and comparing MD5 checksums for the original backup file at your client's place, and the file on the USB drive. Here's one command line utility to do that.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply