From: Sven <sven@shelldog.de>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Timeouts while creating backups on PBS
Date: Fri, 10 Mar 2023 16:02:09 +0100 [thread overview]
Message-ID: <4443ef0f136aed8ca4ef76b9de88677a@shelldog.de> (raw)
Hello
we have several clusters (~250 VMs) attached to one PBS and run daily
backups. Each day, there are random timeouts causing some backups to
fail.
I've disabled the instant verification process to reduce IO-load on the
PBS during that time. The timeouts are gone since then.
Because we do want to have verified backups, we tried out scheduled
verification tasks. Then we have the problem, that it takes to long
(>1d) to verify all ~250 new snapshots sequentially. 50 parallel verify
jobs works well.
My current idea is to write a custom scheduler to make sure that there
is a custom amount of verify jobs simultaneously when no backups are
running.
Is there a better way I don't see? If I may place a feature request: It
would be nice to be able to specify how many verify jobs can work
simultaneously.
Thanks!
Sven
next reply other threads:[~2023-03-10 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 15:02 Sven [this message]
[not found] ` <mailman.74.1678721342.446.pve-user@lists.proxmox.com>
2023-03-13 17:07 ` Victor Rodriguez
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=4443ef0f136aed8ca4ef76b9de88677a@shelldog.de \
--to=sven@shelldog.de \
--cc=pve-user@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