Changing compression level does not seem to reduce the overall repo size #8073
-
Hello, So, I just started to use borg. Question: Scenario:
Let's say I decided to delete the first archive and run Real Scenario:
When I ran Vorta UI app, it shows the second archive is only 0.6MB size: While, from the command line:
Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
The complete faq entry: Can I safely change the compression level or algorithm? The compression level and algorithm don’t affect deduplication. Chunk ID hashes are calculated before compression. New compression settings will only be applied to new chunks, not existing chunks. So it’s safe to change them. |
Beta Was this translation helpful? Give feedback.
-
To answer your question: yes, because the 2nd archive references most chunks that were produced by the 1st archive creation. Only the different, new chunks were compressed using the new algorithm. If you want to globally recompress, borg 1.x only has borg2 will have a more efficient way to globally recompress. |
Beta Was this translation helpful? Give feedback.
To answer your question: yes, because the 2nd archive references most chunks that were produced by the 1st archive creation. Only the different, new chunks were compressed using the new algorithm.
If you want to globally recompress, borg 1.x only has
borg recreate
, but it is rather slow / inefficient.borg2 will have a more efficient way to globally recompress.