KurlesHS/restic
1
0
Fork 0
forked from TrueCloudLab/restic
Code Pull requests Activity

Merge pull request #3822 from JsBergbau/doc-max-compression

Browse source 
Added hint for --compression max in migration process
This commit is contained in:
MichaelEischer 2022-07-12 23:02:45 +02:00 committed by GitHub
commit d71b29221b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/045_working_with_repos.rst
View file

@ -320,4 +320,7 @@ parameter, see :ref:`customize-pruning` for more details.
File contents stored in the repository will not be rewritten, data from new File contents stored in the repository will not be rewritten, data from new
backups will be compressed. Over time more and more of the repository will backups will be compressed. Over time more and more of the repository will
be compressed. To speed up this process and compress all not yet compressed be compressed. To speed up this process and compress all not yet compressed
data, you can run ``prune --repack-uncompressed``. data, you can run ``prune --repack-uncompressed``. When you plan to create
your backups with maximum compression, you should also add the
``--compression max`` flag to the prune command. For already backed up data,
the compression level cannot be changed later on.