Data Decompression Error

Forum for users of Redgate's SQL Backup tool

Data Decompression Error

Postby Gordon » Wed Oct 07, 2009 11:16 am

Hi

I am having some issues restoring one of my databases. I am backing up using the command line syntax via a stored procedure, copying the backup to a remote server and then restoring again using the comman line.

The backup seems fine yet the restore fails with a decompression error. Here are the backup and restore logs:

SQL Backup log file 5.3.0.178

-SQL "BACKUP DATABASE [BV] TO DISK = 'd:\\LogShipping\\BV\\BV_Full_Backup.sqb' WITH NAME = 'Database (BV) Full', INIT, ERASEFILES_ATSTART = 10h, COMPRESSION = 1 " -E

----------------------- PROCESSES COMPLETED SUCCESSFULLY --------------------

06/10/2009 18:01:00: Backing up BV (full database) to:
06/10/2009 18:01:00: d:\\LogShipping\\BV\\BV_Full_Backup.sqb

06/10/2009 18:01:01: Deleting old backup file: d:\\LogShipping\\BV\\BV_Full_Backup.sqb
06/10/2009 18:01:01: BACKUP DATABASE [BV] TO VIRTUAL_DEVICE = 'SQLBACKUP_8101F4A8-54AD-4D03-9E12-E45279135696' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (BV) Full', DESCRIPTION = N'Backup on 06/10/2009 18:01:00 Server: AAA Database: BV'

06/10/2009 18:01:57: Database size : 7.708 GB
06/10/2009 18:01:57: Compressed data size: 1.965 GB
06/10/2009 18:01:57: Compression rate : 74.51%

Processed 856128 pages for database 'BV', file 'BV_Data' on file 1.
Processed 6 pages for database 'BV', file 'BV_Log' on file 1.
BACKUP DATABASE successfully processed 856134 pages in 55.195 seconds (127.066 MB/sec).
06/10/2009 18:01:58: SQL Backup process ended.




SQL Backup log file 5.3.0.178

-SQL "RESTORE DATABASE [BV] FROM DISK = 'd:\\logshipping\\BV\\BV_Full_Backup.sqb' WITH NORECOVERY, REPLACE " -E

----------------------------- ERRORS AND WARNINGS -----------------------------


06/10/2009 18:54:43: Restoring BV (database) from:
06/10/2009 18:54:43: d:\\logshipping\\BV\\BV_Full_Backup.sqb

06/10/2009 18:54:43: RESTORE DATABASE [BV] FROM VIRTUAL_DEVICE = 'SQLBACKUP_A92C57CC-141C-4CAD-981E-174159590F64' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , NORECOVERY, REPLACE

06/10/2009 18:55:28: Thread 0 error:
Data decompression error: file may be corrupted
06/10/2009 18:55:28:
SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3183: SQL error 3183: RESTORE detected an error on page (0:0) in database "BV" as read from the backup set.


Using the md5x utility it shows that the hashes are different on each backup. Is this always down to network issues? The network guys can't see any errors during the copy and this is now the 3rd day in a row this has failed.

There are another 15 databases being copied between these servers on a nightly basis and they are being copied across fine. I'm not sure what else to try.

cheers
Gordon
 
Posts: 6
Joined: Thu Aug 04, 2005 4:22 pm

Postby petey » Thu Oct 08, 2009 1:50 am

Did you try copying the backup file manually to the remote server, comparing the MD5 hashes and if they match, try restoring from the file?

Thanks.
Peter Yeoh
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 7
petey
 
Posts: 2295
Joined: Sun Apr 24, 2005 12:34 pm


Return to SQL Backup Previous Versions

Who is online

Users browsing this forum: Google [Bot] and 0 guests

cron