November 18, 2011 at 1:31 pm
Is there any chance there's a backup compression software application running on the server i.e. (HyperBac, Litespeed, etc?). This will give you the same error when you attempt to back up a DB that's been compressed with these types of software applications to a server that doesn't have it installed.
Probably not the issue here, but just wanted to throw it out there. You'd have the same issues taking a backup from SQL 2008 with compression turned on (or accepting the defaul compression in the maintenance plan) and then attempting to restore it to say a SQL 2005 server).
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
November 18, 2011 at 1:35 pm
Regarding the default "server setting for compression"...if it's set up to compress backups in your SQL Server configuration, and you attempt to back it up on a sever that has this option turned off, if the maintenance plans have "Use default server setting", you'd also see this type of error...
They restore no problem on the original server and a couple actually restore if I manually copy over the backups.
Just throwing it out there...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
November 18, 2011 at 3:04 pm
MyDoggieJessie (11/18/2011)
You'd have the same issues taking a backup from SQL 2008 with compression turned on (or accepting the defaul compression in the maintenance plan) and then attempting to restore it to say a SQL 2005 server).
You'd have an issue taking any backup from SQL 2008 and attempting to restore on SQL 2005, but it's not this error. Restoring a SQL 2008 backup to SQL 2005 will get this:
The database was backed up on a server running version 655. That version is incompatible with this server, which is running version 611. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2011 at 3:08 pm
MyDoggieJessie (11/18/2011)
Regarding the default "server setting for compression"...if it's set up to compress backups in your SQL Server configuration, and you attempt to back it up on a sever that has this option turned off, if the maintenance plans have "Use default server setting", you'd also see this type of error...
Huh??
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2011 at 4:47 pm
Thanks to everyone, especially Gila Monster (who put me on the right track):
I ran a checksum (md5deep) on the files before and after the copy over the network and they are different on the destination server. The file is getting corrupted on the destination server.
November 19, 2011 at 2:49 am
stevescanlan (11/18/2011)
I ran a checksum (md5deep) on the files before and after the copy over the network and they are different on the destination server. The file is getting corrupted on the destination server.
Probably due to the network copy rather than the server. Maybe time to get the network admin involved and see if there's a faulty switch/cable anywhere.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply