- Veeam Support Knowledge Base
- Zlib decompression error: [-3] | Failed to decompress LZ4 block
Zlib decompression error: [-3] | Failed to decompress LZ4 block
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
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
Oops! Something went wrong.
Please, try again later.
Challenge
A Backup Job or Restore fails with either of the following errors:
Zlib decompression error: [-3].
or
Failed to decompress LZ4 block:
Cause
When the software reads from a an existing restore point it performs error detection using Cyclic Redundancy Checks (CRC) to validate the data. The error messages list in this article occur when a CRC fails. The error indicates that one or more blocks in the restore point are corrupted.
Solution
Restoring Missing Production Data
If the failing restore was being performed to restore missing production data, please create a Veeam Support Case. Veeam Support has tools that may be able to recover data from a restore point if it is not fully damaged.
Error During Restore
- If The 3-2-1-1-0 Rule best practice was followed, and there are multiple copies of the restore point, try using a different copy.
- If other restore points are available, try restoring from an older full backup or an incremental associated with an older full.
- If a full VM restore was attempted when the error occurred, the corrupted blocks might only affect blocks that prevent the full VM restore, but a Guest OS File Recovery may still be possible.
Error During Backup
- Try forcing the Backup Job to run an Active Full backup. The Active Full will bypass the need to read data from previous backup files.
More Information
- Veeam Backup & Replication's Data Movers use network traffic verification when transfering data between proxies and repositories to detect corruption which might occur. Therefore decompression errors are unlikely to be caused by a malfunctioning NIC, router, or other network device if the repository server is using a local disk (Windows Repository | Linux Repository).
- For Windows Repositories the event log on the repository server may contain Disk Event 7: “The device… has a bad block.” If so, run CHKDSK /F or /R. If additional bad block events occur after running CHKDSK, check the SMART status and consider replacing the disk.
- When backing up to a CIFS share, NFS share, or iSCSI volume, malfunctioning network hardware is a possible cause of corrupted backup files, because Veeam's network traffic verification cannot verify data sent to those destinations.
- Enabling Storage-level corruption guard will cause the backup/backup copy job to perform automatic checks to proactively detect CRC failures due to corrupted backup files.
- If disk failure is a suspected cause of restore point corruption when using a Network Attached Storage device, contact the storage vendor to determine what diagnostics are available.
What is the 3-2-1-1-0 backup rule?
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Verify your email to continue your product download
We've sent a verification code to:
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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.