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 590DA6412E for ; Tue, 1 Mar 2022 13:11:15 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 415761F039 for ; Tue, 1 Mar 2022 13:11:15 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id EA15D1F02D for ; Tue, 1 Mar 2022 13:11:13 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id B08B3462C6 for ; Tue, 1 Mar 2022 13:11:13 +0100 (CET) From: Dominik Csapak To: pbs-devel@lists.proxmox.com Date: Tue, 1 Mar 2022 13:11:12 +0100 Message-Id: <20220301121112.3863237-1-d.csapak@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.155 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: [pbs-devel] [PATCH proxmox-backup] docs: improve tape-backup examples X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2022 12:11:15 -0000 Signed-off-by: Dominik Csapak --- thanks @thomas for looking over it docs/tape-backup.rst | 43 ++++++++++++++++++++----------------------- 1 file changed, 20 insertions(+), 23 deletions(-) diff --git a/docs/tape-backup.rst b/docs/tape-backup.rst index 5d4ce444..1511ba32 100644 --- a/docs/tape-backup.rst +++ b/docs/tape-backup.rst @@ -987,11 +987,10 @@ Here are a few example setups for how to manage media pools and schedules. This is not an exhaustive list, and there are many more possible combinations of useful settings. -Simple Setup -~~~~~~~~~~~~ +Single Continued Media Set +~~~~~~~~~~~~~~~~~~~~~~~~~~ -The most simple setup, always continue the media-set and never expire. -All backups are stored on a single media set and never deleted. +The most simple setup: always continue the media-set and never expire. Allocation policy: continue @@ -999,20 +998,22 @@ Allocation policy: Retention policy: keep -Such a simple setup has the advantage that it uses not much space, and -since there is only one media-set, it is easy to manage. On the other hand, -it is prone to errors. If a single tape fails, all backups that uses chunks -from that tape will not be restorable. If you want to start a new media-set -manually, you can set the currently writable media of the set either to -'full', or set the location to an offsite vault. In that case, a new -media-set will be created. +This setup has the advantage of being easy to manage and is re-using the benefits +from deduplication as much as possible. But, it's also prone to a failure of +any single tape, which would render all backups referring to chunks from that +tape unusable. + +If you want to start a new media-set manually, you can set the currently +writable media of the set either to 'full', or set the location to an +offsite vault. Weekday Scheme ~~~~~~~~~~~~~~ -A slightly more complex scheme, where the goal is to have a tape for each -weekday, e.g. from Monday to Friday. This can be solved by having a seperate -media pool for each day, so 'Monday', 'Tuesday', etc. +A slightly more complex scheme, where the goal is to have an independent +tape or media set for each weekday, for example from Monday to Friday. +This can be solved by having a separate media pool for each day, so 'Monday', +'Tuesday', etc. Allocation policy: should be 'mon' for the 'Monday' pool, 'tue' for the Tuesday pool and so on. @@ -1020,12 +1021,12 @@ Allocation policy: Retention policy: overwrite -There should be a (or more) tape-backup jobs for each pool on the correspondig -weekday. This scheme is still easily managable with one media set per weekday, +There should be a (or more) tape-backup jobs for each pool on the corresponding +weekday. This scheme is still very manageable with one media set per weekday, which can even be taken off site easily. -Staggered Pools -~~~~~~~~~~~~~~~ +Multiple pools with different policies +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Alternatively, more complex setups are possible with multiple media pools and different allocation and retention policies. @@ -1038,11 +1039,7 @@ Allocation policy: Retention policy: 3 weeks -This creates a new media set each week, and expires them after the 4th -media set. - -Then in addition, there could be a yearly pool that only gets allocated -once a year, but will not be expired (e.g. for long-term archival purposes): +And another pool with yearly allocation that does not expire: Allocation policy: yearly -- 2.30.2