September 24, 2010 at 1:22 pm
Curious if anyone has ran into this issue and what they did to resolve it:
I randomly get a "bad" txn log file which prevents the restore job from restoring. When I run restore verifyonly on the file from Source Server it comes back valid. But when I run verify on the Destination copy I get:
Msg 3242, Level 16, State 1, Line 1
The file on device 'd:\shippedlogs\smart2otrinity\Smart2oTrinity_20100923024507.trn' is not a valid Microsoft Tape Format backup set.
Msg 3013, Level 16, State 1, Line 1
VERIFY DATABASE is terminating abnormally.
Now of course when I rename the file, SQL logshipping is smart enough to "catch up" by copying the file again and MOST of the time it works fine. I know what most of you are thinking and yes, I have elliminated the following:
-- copy the file to a local drive on the destination server (which rules out destination storage)
-- copy the file to a different SAN device
-- copy the file to a local drive on the SOURCE server (which according to the sysadmin rules out Network)
-- I even copied the file MANUALLY through windows explorer (this even failed one time)
Again, the txn log backups on the Source server have ALWAYS come back successful on the verify test, it is only the copied version of the file. And again there is no specific window of when I will get a bad file.
As the never ending saga between SysAdmin and DBA continues, they think it is something internal to SQL and of course I am exhausted with chasing my tail because he thinks the storage is smart enough to let them know when something is wrong and therefore no need to run any diagnostic tests on the storage/network/network cards!!
Any suggestions (including a new cognac to calm my nerves) would be greatly appreciated.
September 24, 2010 at 1:27 pm
its a copy process causing the errors so definitely not internal to SQL. Unlikely to be the SAN either.
As it is intermittent and happens to a file being moved between servers I would suspect the network, you may be occasionally losing packets.
see if you persuade the network guys to run a sniffer program.
---------------------------------------------------------------------
September 24, 2010 at 1:34 pm
George is Right. Please check if the file is getting corrupted during the transfer over the network.
Thank You,
Best Regards,
SQLBuddy
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply