Signed-off-by: Fiona Ebner <f.eb...@proxmox.com>
---
Changes in v3:
* rebase on current master
vzdump.adoc | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/vzdump.adoc b/vzdump.adoc
index 8dc49f5..682c9d1 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -214,13 +214,13 @@ the behaviour for catching up. By enabling the `Repeat
missed` option
(`repeat-missed` in the config), you can tell the scheduler that it should run
missed jobs as soon as possible.
-There are a few settings for tuning backup performance not exposed in the UI.
-The most notable is `bwlimit` for limiting IO bandwidth. The amount of threads
-used for the compressor can be controlled with the `pigz` (replacing `gzip`),
-respectively, `zstd` setting. Furthermore, there are `ionice` and, as part of
-the `performance` setting, `max-workers` (affects VM backups only) and
-`pbs-entries-max` (affects container backups only). See the
-xref:vzdump_configuration[configuration options] for details.
+There are a few settings for tuning backup performance (some not exposed in the
+UI). The most notable is `bwlimit` for limiting IO bandwidth. The amount of
+threads used for the compressor can be controlled with the `pigz` (replacing
+`gzip`), respectively, `zstd` setting. Furthermore, there are `ionice` (when
the
+BFQ scheduler is used) and, as part of the `performance` setting, `max-workers`
+(affects VM backups only) and `pbs-entries-max` (affects container backups
+only). See the xref:vzdump_configuration[configuration options] for details.
[[vzdump_retention]]
Backup Retention
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
