From: Hermann Himmelbauer <hermann@qwer.tk>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Proxmox PBS: Recommended task schedules (Prune, GC, Verifiy)?
Date: Sat, 29 Oct 2022 12:25:05 +0200 [thread overview]
Message-ID: <dab4831a-3277-2637-4ddb-b4eb8d18d61d@qwer.tk> (raw)
Dear Proxmox users,
I am currently configuring a PBS server. For the retention, I used the
values from the following page:
https://pbs.proxmox.com/docs/maintenance.html
keep-last:3, keep-daily:30, keep-weekly: 8, keep-monthly: 11, keep-yearly:9
This looks like a decent retention scenario. The underlying datastore is
ZFS, approx. 40TB.
The backups to my PBS-Server is done at night, starting at 1:00 from a
PVE-Cluster. The backup itself runs for approx. 5 hours.
Working great, o.k. - now I need to configure the following tasks:
- Prune
- Garbage Collection
- Verfiy
Well, it's now really unclear to me when and how often I should do these
tasks? Do I have to ensure in some way that these tasks don't overlap?
Thinking in non-overlapping terms, I'd do it like this:
- Prune: daily at 6:00
- GC: daily at 11:00
- Verify: daily at 15:00
Or is it better to simply do it like that:
- Prune: hourly
- GC: hourly
- Verfiy: hourly
Any hints?
Best Regards,
Hermann
P.S.: I think it would be a great addition to the manual to put some
recommendations / best practices there.
--
Hermann Himmelbauer
Martinstraße 18/2
3400 Klosterneuburg
Mobile: +43-699-11492144
E-Mail: hermann@qwer.tk
GPG/PGP: 299893C7 (on keyservers)
next reply other threads:[~2022-10-29 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 10:25 Hermann Himmelbauer [this message]
2022-10-29 11:40 ` Roland
2022-10-29 13:02 ` RundIT, Service
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=dab4831a-3277-2637-4ddb-b4eb8d18d61d@qwer.tk \
--to=hermann@qwer.tk \
--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 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.