From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] backup: mention where fleecing can be configured
Date: Mon, 29 Apr 2024 16:49:21 +0200 [thread overview]
Message-ID: <20240429144921.454037-1-f.ebner@proxmox.com> (raw)
Reported in the community forum:
https://forum.proxmox.com/threads/145955/post-658380
Signed-off-by: Fiona Ebner <f.ebner@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
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-04-29 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 14:49 Fiona Ebner [this message]
2024-07-03 12:51 ` [pve-devel] applied: " Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240429144921.454037-1-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal