vzdump: fleecing: rephrase manual vzdump example

and move the example command from inline to a block

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
This commit is contained in:
Aaron Lauterer 2024-07-11 13:07:31 +02:00
parent c67a94fcda
commit 703300b980

View File

@ -149,11 +149,14 @@ 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 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. 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 To manually start a backup of VM `123` with fleecing images created on the
fleecing, with fleecing images created on the storage `local-lvm`. As always, storage `local-lvm`, run
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 vzdump 123 --fleecing enabled=1,storage=local-lvm
configured in the 'Advanced' tab when editing a backup job.
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 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 discard support. Examples are LVM-thin, RBD, ZFS with `sparse 1` in the storage