April 6, 2012 at 4:00 am
Hi All,
We have a strange issue with a particular DB. Backup from this particular database is getting corrupted everytime we take whether using litespeed or native to D drive or C drive ,the backup we are getting is corrupted one. We have run DBCC CHECKDB on database and it came clean.
DB is around 600GB in size
Please help
TIA
April 6, 2012 at 4:17 am
How are you determining that the backup is corrupt? What's the precise error?
Are you using checksum when you run the backup? If not, try running the backup using that. You'll get an error at the page that is failing.
This sounds like it's possibly a hardware issue. Have you run any diagnostics against the disks themselves?
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
April 6, 2012 at 5:19 am
Thanks for the quick reply
We are runninng backup using litespeed. when took using sql native tool i select the checksum option .both litespoeed and native returned corrupted backups
GOt error when run RESTORE VERIFYONLY
Msg 3241, Level 16, State 0, Line 1
The media family on device 'D:\machan.bak' is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 1
VERIFY DATABASE is terminating abnormally.
We tried changing the drive even then result was same
We have taken many other backups to the same location without any issue.
April 6, 2012 at 5:38 am
RESTORE VERIFYONLY will fail with a Litespeed backup. That's expected.
Hmmm... When you run the native backup using checksum, you're not getting an error? But if you run restore it fails. That's pretty odd. It suggests that the error is only in the header, not the writes.
The error implies that the file isn't even a backup file. Do you have any other third party apps on the server that might be interfering?
When you run the backup itself, are you doing a complete replace of the file? You're not adding a backup to an existing backup set right? If so, it could just be the first one that's corrupted.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
April 6, 2012 at 5:54 am
We are taking fresh backup not appending to any existing one.
Can i recommed team to check the disk and IO subsystems? If yes could you please let me know what exactly we need to check on disk and IO subsystem.
Thanks in Advance.
April 6, 2012 at 6:33 am
If other backups are working on the same devices there may not be anything to check.
At this point, I'd call Microsoft support. I mean, I'm not there and I can't see what you can see, but assuming it's a straight backup, no third party tools, the database is not corrupt, the backups are passing checksums, other backups from other databases on the same server are working.... I'm not sure what else to look for.
Oh, one other thing, are you running the latest service pack? Once that's eliminated, time for a call to Microsoft.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply