[pve-devel] [PATCH docs] backup: mention where fleecing can be configured

[Fiona Ebner]

Reported in the community forum:
https://forum.proxmox.com/threads/145955/post-658380

Signed-off-by: Fiona Ebner <f.ebner at proxmox.com>
---
 vzdump.adoc | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/vzdump.adoc b/vzdump.adoc
index 79d4bbc..9b1cb61 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -148,8 +148,12 @@ sectors will be limited by the speed of the backup target.
 With backup fleecing, such old data is cached in a fleecing image rather than
 sent directly to the backup target. This can help guest IO performance and even
 prevent hangs in certain scenarios, at the cost of requiring more storage space.
+
 Use e.g. `vzdump 123 --fleecing enabled=1,storage=local-lvm` to enable backup
-fleecing, with fleecing images created on the storage `local-lvm`.
+fleecing, with fleecing images created on the storage `local-lvm`. As always,
+you can set the option for specific backup jobs, or as a node-wide fallback via
+the xref:vzdump_configuration[configuration options]. In the UI, fleecing can be
+configured in the 'Advanced' tab when editing a backup job.
 
 The fleecing storage should be a fast local storage, with thin provisioning and
 discard support. Examples are LVM-thin, RBD, ZFS with `sparse 1` in the storage
-- 
2.39.2