-
-
Notifications
You must be signed in to change notification settings - Fork 757
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: support for lzip compression #827
Comments
It's description reads like it's aimed at replacing the ".gz" or ".bz2" in ".tar.gz" for backup jobs, i.e. large, unencrypted archives (on unencrypted storage). It would need to be tested whether it has any advantage (compression ratio to speed or similar) over LZ4, zlib or LZMA. The description says it uses an LZMA scheme so I'd expect similar performance (which in most cases isn't better than zlib; LZMA works better for larger amounts of data) The additional integrity checking is unnecessary in Borg, since (HMAC-)SHA-256 is already used for verifying data integrity (with a probability that isn't 100 %, but can't be reasonably written down other than 100 %, to detect errors[1]). The recovery won't work for encrypted repositories - a flipped bit on-disk has a large probability of completely garbling the whole block (and failing HMAC, anyway). [1] Ask a calculator about |
There is already #225 to discuss redundancy / error correction options. I agree with @enkore that lzip does not seem to offer anything else new than that. And I guess we'll rather want error correction on a separate layer, not mangled into a specific compression method, so it can also be used without compression or with one of the existing compression methods. Thus, I am closing this. |
See also #1633. |
it would be nice to have borgbackup offer lzip compression.
The text was updated successfully, but these errors were encountered: