From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id B8A8C70D73 for ; Wed, 15 Jun 2022 10:37:39 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id AAD6D27B59 for ; Wed, 15 Jun 2022 10:37:39 +0200 (CEST) Received: from hermes.qwer.tk (hermes.qwer.tk [93.82.198.100]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2B46127B4D for ; Wed, 15 Jun 2022 10:37:39 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by hermes.qwer.tk (Postfix) with ESMTP id 9323C1A49EA for ; Wed, 15 Jun 2022 10:31:03 +0200 (CEST) X-Virus-Scanned: by amavisd-new at qwer.tk Received: from hermes.qwer.tk ([127.0.0.1]) by localhost (hermes.qwer.tk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12U7-LN1O0md for ; Wed, 15 Jun 2022 10:31:02 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by hermes.qwer.tk (Postfix) with ESMTP id 7E6DF1A4784 for ; Wed, 15 Jun 2022 10:31:02 +0200 (CEST) Received: from [192.168.50.79] (daidalos.qwer.tk [192.168.50.79]) by hermes.qwer.tk (Postfix) with ESMTP id 1E18D1A2E9E for ; Wed, 15 Jun 2022 10:31:02 +0200 (CEST) Message-ID: <7497486c-aea9-0f46-3d45-b3cc88619de7@qwer.tk> Date: Wed, 15 Jun 2022 10:31:02 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 To: pve-user@lists.proxmox.com Content-Language: de-DE From: Hermann Himmelbauer Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.380 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [PVE-User] PBS - Verification, Garbage Collection etc. - best practices? X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2022 08:37:39 -0000 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)