From: Victor Rodriguez <vrodriguez@soltecsis.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Timeouts while creating backups on PBS
Date: Mon, 13 Mar 2023 18:07:37 +0100 [thread overview]
Message-ID: <83c0b99e-f2ae-009d-db11-51b93575b227@soltecsis.com> (raw)
In-Reply-To: <mailman.74.1678721342.446.pve-user@lists.proxmox.com>
> 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.
AFAIK, a verification job will not re-verify a chunk that has been
verified already by that same job, meaning that a verify job for 2+
snapshots should be more efficient that a verify job for each snapshot
or doing an inmediate verify after each backup.
On the other hand, verifies are processed sequentially, so even if your
host has enough resources the job will take some time to finish. The
approach I currently use is to get a few verify jobs for each namespace
and start them at the same time if possible.
--
prev parent reply other threads:[~2023-03-13 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 15:02 Sven
[not found] ` <mailman.74.1678721342.446.pve-user@lists.proxmox.com>
2023-03-13 17:07 ` Victor Rodriguez [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=83c0b99e-f2ae-009d-db11-51b93575b227@soltecsis.com \
--to=vrodriguez@soltecsis.com \
--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