Hi everyone, yesterday I needed to restore an account from a daily legacy backup, on a server which had "use pigz" option enabled during backup and during restore. I terminated the account and ran legacy backup restore from WHM. And to my surprise, restoration failed with tar CRC error message. Tried again, failed again: unable to unpack archive. CRC error mesage. HDD had enough space. I successfully restored the same account on the same box many times before, restoration never failed in past. To test tar.gz archive in question, I copied it to a Windows machine, unpacked it with WinRar -- no errors found. Then tested the archive on the server via shell by unpacking it with gunzip to dev/null - no errors found. How is this possible? Is this preventable? Can we have a feature in cPanel that checks created .tar.gz archives after backup complete for integrity (for CRC errors)? Also, some archive software, for example, WiinRar have a "recovery record" feature, description from Wikipedia: they can add extra bytes to archive to improve its "durability". Can we have a feature in cPanel that creates backup archives with extra recovery record?