From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/1] qmrestore: document pbs restore environment variables
Date: Mon, 14 Jul 2025 10:34:39 +0200 [thread overview]
Message-ID: <20250714083439.1240349-3-d.csapak@proxmox.com> (raw)
In-Reply-To: <20250714083439.1240349-1-d.csapak@proxmox.com>
so users know they can override the concurrency settings.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
qmrestore.adoc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/qmrestore.adoc b/qmrestore.adoc
index 37f185a..7f0b4a3 100644
--- a/qmrestore.adoc
+++ b/qmrestore.adoc
@@ -27,6 +27,11 @@ Restore the QemuServer vzdump backup `archive` to virtual machine
`vmid`. Volumes are allocated on the original storage if there is no
`storage` specified.
+When restoring from PBS, you can control the number of concurrent chunk fetches
+with the environment variable `PBS_RESTORE_FETCH_CONCURRENCY` (default=16) and
+the maximum number of threads to be used with `PBS_RESTORE_MAX_THREADS`
+(default=4).
+
ifdef::manvolnum[]
include::pve-copyright.adoc[]
endif::manvolnum[]
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-14 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 8:34 [pve-devel] [PATCH docs/proxmox-backup-qemu 0/2] increase concurrency for pbs-restore Dominik Csapak
2025-07-14 8:34 ` [pve-devel] [PATCH proxmox-backup-qemu 1/1] restore: make chunk loading more parallel Dominik Csapak
2025-07-14 12:17 ` Adam Kalisz via pve-devel
2025-07-15 19:18 ` [pve-devel] applied: " Thomas Lamprecht
2025-07-16 11:51 ` Adam Kalisz via pve-devel
[not found] ` <0fb686395742d507041329058c1b59134701bde2.camel@notnullmakers.com>
2025-07-17 15:57 ` Thomas Lamprecht
2025-07-14 8:34 ` Dominik Csapak [this message]
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=20250714083439.1240349-3-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pbs-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox