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 C49D763D51 for ; Mon, 28 Feb 2022 12:20:41 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BBA486010 for ; Mon, 28 Feb 2022 12:20:11 +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 817DB6002 for ; Mon, 28 Feb 2022 12:20:10 +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 5AB5C41C56 for ; Mon, 28 Feb 2022 12:20:10 +0100 (CET) From: Dominik Csapak To: pbs-devel@lists.proxmox.com Date: Mon, 28 Feb 2022 12:20:08 +0100 Message-Id: <20220228112008.3364833-2-d.csapak@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20220228112008.3364833-1-d.csapak@proxmox.com> References: <20220228112008.3364833-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.156 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 v2 2/2] docs: add tape schedule 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: Mon, 28 Feb 2022 11:20:41 -0000 just a few examples how one could configure tape pools and jobs. Signed-off-by: Dominik Csapak --- changes from v1: * clarified how to manually trigger a new media-set in the simplest case * reworded last example by removing 'rotation' (if a tape is rotated depends on how many tapes there are in the pool) docs/tape-backup.rst | 74 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) diff --git a/docs/tape-backup.rst b/docs/tape-backup.rst index ae597d3d..5d4ce444 100644 --- a/docs/tape-backup.rst +++ b/docs/tape-backup.rst @@ -979,3 +979,77 @@ This command does the following: - run drive cleaning operation - unload the cleaning tape (to slot 3) + +Example Setups +-------------- + +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 +~~~~~~~~~~~~ + +The most simple setup, always continue the media-set and never expire. +All backups are stored on a single media set and never deleted. + +Allocation policy: + continue + +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. + +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. + +Allocation policy: + should be 'mon' for the 'Monday' pool, 'tue' for the Tuesday pool and so on. + +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, +which can even be taken off site easily. + +Staggered Pools +~~~~~~~~~~~~~~~ + +Alternatively, more complex setups are possible with multiple media pools and +different allocation and retention policies. + +An example would be to have a media pool with weekly allocation: + +Allocation policy: + mon + +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): + +Allocation policy: + yearly + +Retention policy: + keep + +In combination with suited prune settings and tape backup schedules, this +achieves long-term storage of some backups, while keeping the current +backups on smaller media sets that get expired every 4 weeks. -- 2.30.2