What are the challenges you face when working across database platforms? Take the survey

Log Shipping failing

ToehoToeho Posts: 73
edited November 20, 2007 11:08AM in SQL Backup Previous Versions
I am again having issues with log shipping and Sql Backup and starting to become extreamly frustraded as it takes alomost a week to get the tape sent to the dr site and then getting everything back ito sync, this is now the 4th time in the past 3 months that I have had to do this.

It would appear that if the log backup on the source server has any type of error, no matter what then the log will not restore on the source. I am getting the following error when trying to restore a log file that had the following error durring the backup. The backup file is now corupt because it couldnt copy it as part of the sql backup command??

Backup error
SQL Backup log file
11/18/2007 2:05:01 PM: Backing up PRD (transaction log) to:
11/18/2007 2:05:01 PM: H:\Backups\PRD_11182007_140501_LOG.sqb

11/18/2007 2:05:01 PM: BACKUP LOG [PRD] TO DISK = 'H:\Backups\<AUTO>.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', PASSWORD = 'XXXXXXXXXX', KEYSIZE = 256, ERASEFILES = 6, MAILTO_ONERROR = 'william.r.stevenson@acs-inc.com', COPYTO = '\\\LogshipPRD', FILEOPTIONS = 1, COMPRESSION = 2

11/18/2007 2:05:02 PM: Backup data size : 12.063 MB
11/18/2007 2:05:02 PM: Compressed data size: 5.606 MB
11/18/2007 2:05:02 PM: Compression rate : 53.52%

Processed 1466 pages for database 'PRD', file 'PRDLOG1' on file 1.
BACKUP LOG successfully processed 1466 pages in 0.780 seconds (15.392 MB/sec).
11/18/2007 2:05:56 PM: Warning 141: COPYTO error: Unable to copy H:\Backups\PRD_11182007_140501_LOG.sqb to \\\LogshipPRD\PRD_11182007_140501_LOG.sqb (The operation completed successfully).
11/18/2007 2:05:57 PM: Mail sent successfully to: xxx

Restore Error:
SQL Backup v5.2.0.2824
Restoring PRD (transaction logs) from:

Thread 0 error:
Data decompression error: ZLib decompression error: data error

SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
SQL error 3241: SQL error 3241: The media family on device 'SQLBACKUP_BEBE8CA1-8CE0-455A-8316-8952D8AAC1ED' is incorrectly formed. SQL Server cannot process this media family.

SQL Backup exit code: 790
SQL error code: 3241

(11 row(s) affected)

name value

exitcode 790
sqlerrorcode 3241

(2 row(s) affected)


Sign In or Register to comment.