1-800-691-1991 | 9am - 8pm ET
EN

Zlib decompression error: [-3] | Failed to decompress LZ4 block

KB ID: 1795
Product: Veeam Backup & Replication
Version: 5.x, 6.x, 7.x, 8.x, 9.x
Published: 2013-07-29
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Backup or restore fails with either of the following errors:

Error: Client error: Zlib decompression error: [-3].

OR


Error: Client error: Failed to decompress LZ4 block: Incorrect decompression result or length

 

Cause

Cyclic Redundancy Check (CRC) failed while extracting data from a backup file. This indicates that one or more blocks in that file are corrupted.
 
Typically this error indicates hardware malfunction during storage or transmission of the backup file. Most types of storage are subject to a small degree of unrecoverable failure – this is commonly called Bit Rot.

Solution

If you are attempting restore and have multiple copies of the backup file, try using a different copy. If you have other restore points, try an older full backup or an incremental associated with an older full. If you are unable to recover the complete VM, file level recovery may still be possible.
 
If the error is encountered during backup, try running an active full backup. This will bypass the need to read data from previous backup files.
 
The Windows event log on the repository server may contain Disk Event 7: “The device… has a bad block.” If so, run CHKDSK /F or /R. A small number of bad blocks are normal on most storage devices. If additional bad block events occur after running CHKDSK, check the SMART status and consider replacing the disk. If using a Network Attached Storage device, contact your storage vendor to determine what diagnostics are available.

More information

Veeam Backup & Replication 6.5 added network traffic verification in order to detect corruption which might occur when sending data from a proxy to a repository or other proxy. Decompression errors in 6.5 and later are unlikely to be caused by a malfunctioning NIC, router, or other network device if the repository server is using a local disk. However, when backing up to a CIFS share, malfunctioning network hardware may be the cause of corrupted files.
 
Synthetic full backups and reverse incremental backups both have the potential to copy data from corrupted backup files. Active full backups do not copy any data from existing backup files. Although it is best to perform periodic full-VM recovery tests, you can schedule monthly or quarterly active full backups to reduce the possibility that your latest backup contains corrupted data.


https://www.veeam.com/wp-data-corruption-types-and-countermeasures.html
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.