forked from TrueCloudLab/restic
Added hint for --compression max in migration process
Added hint for --compression max in migration process. Since this is a onetime process users should be aware of this and consider this step.
This commit is contained in:
parent
98a3125ce4
commit
8d3f04aefa
1 changed files with 6 additions and 1 deletions
|
@ -320,4 +320,9 @@ 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 creating
|
||||||
|
your backups with maximum compression you should also use this flag
|
||||||
|
when doing this step since you can't switch to maximum compression later.
|
||||||
|
Complete command for repacking with maximum compression:
|
||||||
|
``restic prune --repack-uncompressed --compression max``.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue