When you get a Decompression failed it could mean a couple different things. It is possible that there is something incomplete in the file or chain whenShadowProtect attempts to read it, or the image is corrupt.
Here are some items that you may want to check out:
- When you get dependency verification failed. First try to move the file out of the directory and back in to force a reverification of the file. If that fixes it we are good, if not run image.exe qp. Here are the instructions: How To: Using Image QP to check the restore chain
- If the file is listed in the output of "image qp" you will need to follow with these steps.
- To resolve these types of errors, move (NOT DELETE) the files that are being reported as bad out of the chain. Then use the "Start Processing" button on the left side of the ImageManager window. (This will force ImageManager to sync the image chain with the ImageManager database file.)
- If these errors return after moving the files, paste them back into the chain and process ImageManager again. (This confirms the chain is broken)
- You then need to remove all the images from the point of the chain that has failed to the end of the chain.
- If the file is not listed in the image qp then you should remove the file that are being reported as bad out of the chain, and then use the "Start Processing" button on the left side of the ImageManager window. It should recreate the consolidated file that is needed.
- When you next run ShadowProtect, a DiffGen may run to "heal" then chain. The DiffGen will take much longer than normal so allow it to complete.
- If the errors disappear then the old images were not needed. They may be safely deleted.
- Make sure you are running the latest version of ImageManager, version 6.0.x
- Look at Agent setting to see what version you are using.
You can also take a look at this article as well: