From: Hermann Himmelbauer <hermann@qwer.tk>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] PBS - Verification, Garbage Collection etc. - best practices?
Date: Wed, 15 Jun 2022 10:31:02 +0200 [thread overview]
Message-ID: <7497486c-aea9-0f46-3d45-b3cc88619de7@qwer.tk> (raw)
Dear Proxmox / PBS users,
I have the following scenario:
- One Proxmox cluster that backups to PBS server "A" (daily)
- An offsite Proxmox host that backups to an offsite PBS server "B" (daily)
- A daily sync job that syncs the backups from the first PBS server to
the offsite server
This works so far. What I now wonder is, how to do garbage collection,
verification, Pruning jobs etc. Are there any recommendations, or some
other "best practices"?
My vague initial idea would be:
- Set some retention on PBS "A" and do garbage collection / pruning
daily, at times when the backup and PBS A->B syncing does not run
- Set the sync from A->B in a way that vanished backups are not deleted
(so that in a case that a hacker deletes backups on Server A they are
not deleted on B).
- Set a longer retention on PBS "B" than on "A" and do garbage
collection / pruning daily, at times when the backup and PBS A-> B
syncing does not run
- Do verification somewhere in between
Any ideas on this plan?
Best Regards,
Hermann
--
hermann@qwer.tk
PGP/GPG: 299893C7 (on keyservers)
reply other threads:[~2022-06-15 8:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7497486c-aea9-0f46-3d45-b3cc88619de7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox