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 47E91D3B5 for ; Wed, 30 Nov 2022 16:01:29 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3150420103 for ; Wed, 30 Nov 2022 16:01:29 +0100 (CET) Received: from lana.proxmox.com (unknown [94.136.29.99]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Wed, 30 Nov 2022 16:01:28 +0100 (CET) Received: by lana.proxmox.com (Postfix, from userid 10043) id D61492C278D; Wed, 30 Nov 2022 16:01:26 +0100 (CET) From: Stefan Hanreich To: pbs-devel@lists.proxmox.com Date: Wed, 30 Nov 2022 16:01:02 +0100 Message-Id: <20221130150102.242374-8-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20221130150102.242374-1-s.hanreich@proxmox.com> References: <20221130150102.242374-1-s.hanreich@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.317 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods NO_DNS_FOR_FROM 0.001 Envelope sender has no MX or A DNS records RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pbs-devel] [PATCH proxmox-backup v2 7/7] Add documentation for prune options in Sync Jobs 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: Wed, 30 Nov 2022 15:01:29 -0000 Short explanation on where/how to set the options for the Prune Job in the Web UI/CLI. Signed-off-by: Stefan Hanreich --- docs/managing-remotes.rst | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/managing-remotes.rst b/docs/managing-remotes.rst index 1c52e120..441710f4 100644 --- a/docs/managing-remotes.rst +++ b/docs/managing-remotes.rst @@ -210,3 +210,17 @@ the web interface or using the ``proxmox-backup-manager`` command-line tool: .. code-block:: console # proxmox-backup-manager sync-job update ID --rate-in 20MiB + +Additional Pruning +^^^^^^^^^^^^^^^^^^ +Sync jobs can be configured to run an automatic prune job after their +completion. This can be configured via the Web UI under the tab +**Prune Options** in the **Add** or **Edit** dialogue of Sync Jobs. This can +also be configured using the ``proxmox-backup-manager`` command-line tool: + +.. code-block:: console + + # proxmox-backup-manager sync-job update ID --keep-last 2 + +For more information on how Prune Jobs work, please consult the respective +chapter :ref:`maintenance_pruning` in the documentation. -- 2.30.2