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 E67246C760 for ; Thu, 23 Sep 2021 13:37:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B3D4524D5A for ; Thu, 23 Sep 2021 13:37:45 +0200 (CEST) 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 6613624C43 for ; Thu, 23 Sep 2021 13:37:41 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 3ED8044A75 for ; Thu, 23 Sep 2021 13:37:41 +0200 (CEST) From: Dominik Csapak To: pbs-devel@lists.proxmox.com Date: Thu, 23 Sep 2021 13:37:39 +0200 Message-Id: <20210923113739.4151043-14-d.csapak@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20210923113739.4151043-1-d.csapak@proxmox.com> References: <20210923113739.4151043-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.361 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 Subject: [pbs-devel] [PATCH proxmox-backup v2 13/13] docs: add info about protection flag to client docs 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: Thu, 23 Sep 2021 11:37:45 -0000 and mention that sync/pull does not sync the protected flag Signed-off-by: Dominik Csapak --- docs/backup-client.rst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/backup-client.rst b/docs/backup-client.rst index 02dae100..f18651ef 100644 --- a/docs/backup-client.rst +++ b/docs/backup-client.rst @@ -652,6 +652,25 @@ shows the list of existing snapshots and what actions prune would take. in the chunk-store. The chunk-store still contains the data blocks. To free space you need to perform :ref:`client_garbage-collection`. +It is also possible to protect single snapshots from being pruned or deleted: + +.. code-block:: console + + # proxmox-backup-client snapshot protected update true + +This will set the protected flag on the snapshot and prevent pruning or manual +deletion of this snapshot untilt he flag is removed again with: + +.. code-block:: console + + # proxmox-backup-client snapshot protected update false + +When a group is with a protected snapshot is deleted, only the non-protected +ones are removed and the group will remain. + +.. note:: This flag will not be synced when using pull or sync jobs. If you + want to protect a synced snapshot, you have to manually to this again on + the target :ref:`backup server. .. _client_garbage-collection: -- 2.30.2