attrs: update cephdocs template to quincy

[pve-docs.git] / vzdump.adoc

diff --git a/vzdump.adoc b/vzdump.adoc
index 841cf3d3042b417bf62331ff79e4d532820473c4..ce465295f8d375d5e210d149e989cadaf2bee434 100644 (file)
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -64,7 +64,7 @@ depending on the guest type.
 
 This mode provides the highest consistency of the backup, at the cost
 of a short downtime in the VM operation. It works by executing an
-orderly shutdown of the VM, and then runs a background Qemu process to
+orderly shutdown of the VM, and then runs a background QEMU process to
 backup the VM data. After the backup is started, the VM goes to full
 operation mode if it was previously running. Consistency is guaranteed
 by using the live backup feature.
@@ -92,8 +92,8 @@ https://git.proxmox.com/?p=pve-qemu.git;a=blob_plain;f=backup.txt[here].
 NOTE: {pve} live backup provides snapshot-like semantics on any
 storage type. It does not require that the underlying storage supports
 snapshots. Also please note that since the backups are done via 
-a background Qemu process, a stopped VM will appear as running for a 
-short amount of time while the VM disks are being read by Qemu.
+a background QEMU process, a stopped VM will appear as running for a
+short amount of time while the VM disks are being read by QEMU.
 However the VM itself is not booted, only its disk(s) are read.
 
 .Backup modes for Containers:
@@ -217,7 +217,8 @@ 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 is `ionice`. See the
+respectively, `zstd` setting. Furthermore, there are `ionice` and, as part of
+the `performance` setting, `max-workers` (affects VM backups only). See the
 xref:vzdump_configuration[configuration options] for details.
 
 [[vzdump_retention]]