ZLib decompression error
I've been getting the following error while trying to restore a database.
Thread 0 error:
Data decompression error: ZLib decompressionerror: buffer error
Server: Msg 3031
RESTORE DATABASE is terminating abnormally.
Server: Msg 3203
Read on 'SQLBACKUP_AB98BBB3-D06E-4813-BD04-A840F5565AEO' failed,
status = 995. See the Sql Server error log for more details.
SQL error code: 3203
Any ideas why I'm receiveing this error. It's beginning to happen more and more.
Thanks
Jon
Thread 0 error:
Data decompression error: ZLib decompressionerror: buffer error
Server: Msg 3031
RESTORE DATABASE is terminating abnormally.
Server: Msg 3203
Read on 'SQLBACKUP_AB98BBB3-D06E-4813-BD04-A840F5565AEO' failed,
status = 995. See the Sql Server error log for more details.
SQL error code: 3203
Any ideas why I'm receiveing this error. It's beginning to happen more and more.
Thanks
Jon
Comments
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
MD5: F63F443902C3C2FAAA4FB2A0BDA7A370 > DATA01.sqb
MD5: A60DF2B22A5D3BE79AF329B3355355C8 > DATA02.sqb
MD5: BD779D8C2C5749E20163A28504659CAF > DATA03.sqb
MD5: 48BAECB601A51064025C910F4069B0EC > DATA04.sqb
In the GUI, the restore wizard checks only the header (1KB) of each of the backup files, to ensure that they are SQL Backup files. It does not check the entire contents of the files.
If the files are not too large, do you think you can send me copies of the files?
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
The situation that we're running into is not the fact that we're copying data from machine A to machine B within our network. The problem occurs when we receive a backup of our customer's data to host on our website. The encrypted backups are sent to us across the internet via SSH. When we recieve the data the file size is the same but the checksum for one of the files is off. SQL Backup does not recognize this and starts restoring the data but never finishes and leaves the database in the "Loading" state. This problem is getting worse as we bring more customers on. Is there some way we can escalate this issue that we are running into, because I can only see this issue getting worse as we convert more of our customers over to our new data structure.
The problem is with the incorrect backup file. Some suggestions:
- if running SQL 2005, create the backup using CHECKSUM option. When you receive the backup file, run RESTORE VERIFYONLY using SQL Backup on the files. Only if there were no errors do you run the actual restore. Cost: time to perform the verification.
- generate a checksum of the backup file on the source machine. When the file is copied over, generate another checksum for comparison. Compare before performing the restore. Cost: time to perform the checksum computation.
- before the restore, make a backup of the database. If the restore fails, restore using this backup. Cost: storage to hold the backup file.
- run a restore but to a staging database. If the restore is successful, drop the existing database, and rename the staging database. Cost: storage to hold the staging database.
- compress the backup file using a 3rd-party compression app e.g. winrar. The file will fail to decompress if there were any errors during the file transfer. Cost: time and storage to hold another copy of the compressed file.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
Thanks
And no, I don't own stocks in rarlabs.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8