From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <f.ebner@proxmox.com> 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 D84B596B06 for <pve-devel@lists.proxmox.com>; Tue, 16 Apr 2024 14:10:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B5E2119154 for <pve-devel@lists.proxmox.com>; Tue, 16 Apr 2024 14:10:02 +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 for <pve-devel@lists.proxmox.com>; Tue, 16 Apr 2024 14:10:01 +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 B557A450BE for <pve-devel@lists.proxmox.com>; Tue, 16 Apr 2024 14:10:01 +0200 (CEST) From: Fiona Ebner <f.ebner@proxmox.com> To: pve-devel@lists.proxmox.com Date: Tue, 16 Apr 2024 14:09:57 +0200 Message-Id: <20240416120957.75269-8-f.ebner@proxmox.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20240416120957.75269-1-f.ebner@proxmox.com> References: <20240416120957.75269-1-f.ebner@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.070 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy 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: [pve-devel] [PATCH v4 docs 2/2] backup: clarify where repeat-missed option can be found now X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Tue, 16 Apr 2024 12:10:32 -0000 It was moved to the advanced tab by pve-manager commit ui: backup job: move repeat-missed option to advanced tab Signed-off-by: Fiona Ebner <f.ebner@proxmox.com> --- New in v4. vzdump.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/vzdump.adoc b/vzdump.adoc index fa904cc..8c3ebef 100644 --- a/vzdump.adoc +++ b/vzdump.adoc @@ -210,9 +210,9 @@ together with the backup. Since scheduled backups miss their execution when the host was offline or the pvescheduler was disabled during the scheduled time, it is possible to configure -the behaviour for catching up. By enabling the `Repeat missed` option -(`repeat-missed` in the config), you can tell the scheduler that it should run -missed jobs as soon as possible. +the behaviour for catching up. By enabling the `Repeat missed` option (in the +'Advanced' tab in the UI, `repeat-missed` in the config), you can tell the +scheduler that it should run missed jobs as soon as possible. There are a few settings for tuning backup performance (some of which are exposed in the 'Advanced' tab in the UI). The most notable is `bwlimit` for -- 2.39.2