From c5542ddcd2bf41e0c1039d0c9f91b7021290e1f1 Mon Sep 17 00:00:00 2001 From: "Leo R. Lundgren" Date: Wed, 11 Jan 2023 00:07:50 +0100 Subject: [PATCH] doc: Move and update documentation for --no-scan --- doc/040_backup.rst | 10 ---------- doc/047_tuning_backup_parameters.rst | 9 +++++++++ 2 files changed, 9 insertions(+), 10 deletions(-) diff --git a/doc/040_backup.rst b/doc/040_backup.rst index e038e1485..b9996311d 100644 --- a/doc/040_backup.rst +++ b/doc/040_backup.rst @@ -204,16 +204,6 @@ Combined with ``--verbose``, you can see a list of changes: modified /archive.tar.gz, saved in 0.140s (25.542 MiB added) Would be added to the repository: 25.551 MiB -Disabling Backup Progress Estimation -************************************ - -When you start a backup, restic will concurrently count the number of -files and their total size, which is used to estimate how long it will -take. This will cause some extra I/O, which can slow down backup of -network file systems or fuse mounts. - -- ``--no-scan`` Do not run scanner to estimate size of backup - .. _backup-excluding-files: Excluding Files *************** diff --git a/doc/047_tuning_backup_parameters.rst b/doc/047_tuning_backup_parameters.rst index d348b17ec..adfe3f09c 100644 --- a/doc/047_tuning_backup_parameters.rst +++ b/doc/047_tuning_backup_parameters.rst @@ -19,6 +19,15 @@ values. As the restic commands evolve over time, the optimal value for each para can also change across restic versions. +Disabling Backup Progress Estimation +************************************ + +When you start a backup, restic will concurrently count the number of files and +their total size, which is used to estimate how long it will take. This will +cause some extra I/O, which can slow down backups of network file systems or +FUSE mounts. To avoid this overhead at the cost of not seeing a progress +estimate, use the ``--no-scan`` option which disables this file scanning. + Backend Connections ===================