public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Roland <devzero@web.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
	Hermann Himmelbauer <hermann@qwer.tk>
Subject: Re: [PVE-User] Proxmox PBS: Recommended task schedules (Prune, GC, Verifiy)?
Date: Sat, 29 Oct 2022 13:40:23 +0200	[thread overview]
Message-ID: <a28aaba3-27ce-3c09-7d4a-8f0a2eb185c5@web.de> (raw)
In-Reply-To: <dab4831a-3277-2637-4ddb-b4eb8d18d61d@qwer.tk>

 >Do I have to ensure in some way that these tasks don't overlap?

since proxmox gui/scheduling won't allow serialization of this tasks,
i'm running them via cron/script

# proxmox-backup-manager verify pve-t620_backup --ignore-verified true
--outdated-after 30
# pvesm prune-backups pbs_pve-t620_backup --keep-daily 31 --keep-weekly
8 --keep-monthly 6
# proxmox-backup-manager garbage-collection start pve-t620_backup

regards
Roland



Am 29.10.22 um 12:25 schrieb Hermann Himmelbauer:
> 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.
>
>
>
>
>
>



  reply	other threads:[~2022-10-29 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29 10:25 Hermann Himmelbauer
2022-10-29 11:40 ` Roland [this message]
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=a28aaba3-27ce-3c09-7d4a-8f0a2eb185c5@web.de \
    --to=devzero@web.de \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal