From 8d3f04aefa582fb12962277c210e249a75887b9f Mon Sep 17 00:00:00 2001
From: JsBergbau <37013344+JsBergbau@users.noreply.github.com>
Date: Tue, 12 Jul 2022 00:08:26 +0200
Subject: [PATCH] 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.
---
 doc/045_working_with_repos.rst | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/doc/045_working_with_repos.rst b/doc/045_working_with_repos.rst
index d34b09c08..320861c67 100644
--- a/doc/045_working_with_repos.rst
+++ b/doc/045_working_with_repos.rst
@@ -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
 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``.
+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``.
+