ZLib decompression error

jerryhungjerryhung Posts: 138
edited October 8, 2008 9:53AM in SQL Backup Previous Versions
I got this error when trying to restore from .sqb file to DB
(actually I got the same error Zlib/Buffer error in SQB2MTF)
Data decompression error: ZLib decompression error: data error
Process terminated unexpectedly. Error code: -2139684860

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 "Log" as read from the backup set.

SQL Backup exit code: 790
SQL error code: 3183


The .sqb file is 3.07GB (original MDF is 24GB and growing)
SQLBackup is v5.3.0.178

Server is Windows 2003 R2 x64, SQL Server 2008 Standard RTM x64
Server is Virtual (VMWare) with 3GB RAM
Jerry Hung
DBA, MCITP
· Share on Twitter

Comments

  • peteypetey Posts: 2,358 New member
    Could you please post the contents of the SQL Backup log file for the restore that failed? By default, the log files are stored in C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name>.

    Does your SQL Server 2008 database use the new FILESTREAM feature?

    Is the backup file the original backup file, or is it a copy? If the latter, could you please check if the file is identical to the original? You could use a md5 file hash generator to generate a checksum.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
  • jerryhungjerryhung Posts: 138
    petey wrote:
    Could you please post the contents of the SQL Backup log file for the restore that failed? By default, the log files are stored in C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name>.

    Does your SQL Server 2008 database use the new FILESTREAM feature?

    Is the backup file the original backup file, or is it a copy? If the latter, could you please check if the file is identical to the original? You could use a md5 file hash generator to generate a checksum.

    Here's the log file
    SQL Backup log file 5.3.0.178

    -SQL "RESTORE DATABASE [VerticalsLog] FROM DISK = 'D:\Backup\VerticalsLog.sqb' WITH RECOVERY, MOVE 'VerticalsLog' TO 'E:\SQLData\VerticalsLog.mdf', REPLACE "
    ERRORS AND WARNINGS


    10/3/2008 2:29:07 PM: Restoring VerticalsLog (database) from:
    10/3/2008 2:29:07 PM: D:\Backup\VerticalsLog.sqb

    10/3/2008 2:29:07 PM: RESTORE DATABASE [VerticalsLog] FROM VIRTUAL_DEVICE = 'SQLBACKUP_570CC681-3C68-44F2-9870-E2005C474C68' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , RECOVERY, MOVE 'VerticalsLog' TO 'E:\SQLData\VerticalsLog.mdf', REPLACE

    10/3/2008 2:33:21 PM: Thread 0 error:
    Data decompression error: ZLib decompression error: data error
    Process terminated unexpectedly. Error code: -2139684860
    10/3/2008 2:33:21 PM:
    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 "VerticalsLog" as read from the backup set.

    FILESTREAM is Disabled on both the Source server DB and the Destination server DB

    The file is the original backup file downloaded via the FTP
    Jerry Hung
    DBA, MCITP
    · Share on Twitter
  • peteypetey Posts: 2,358 New member
    The SQL Backup error message suggests that the file is corrupted. Could you please download and run this md5 hash generator on both the original backup file, and the file you downloaded, and compare the hash values? Are they equal?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
  • jerryhungjerryhung Posts: 138
    Never mind the issue

    I re-downloaded a new backup (daily generated)
    MD5 both and they matched
    Restored with SQL Backup, it worked fine


    Thanks
    Jerry Hung
    DBA, MCITP
    · Share on Twitter
Sign In or Register to comment.