From 71ff6b77f03c0a8cabcff437ce86d8a5630cc85f Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Tue, 12 Jul 2022 21:24:40 +0200 Subject: [PATCH] doc: Rework hint to repack with max compression --- doc/045_working_with_repos.rst | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/doc/045_working_with_repos.rst b/doc/045_working_with_repos.rst index 320861c67..f8ff42134 100644 --- a/doc/045_working_with_repos.rst +++ b/doc/045_working_with_repos.rst @@ -320,9 +320,7 @@ parameter, see :ref:`customize-pruning` for more details. 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 be compressed. To speed up this process and compress all not yet compressed -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``. - +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.