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 577D898D3B for ; Tue, 18 Apr 2023 16:59:50 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 37CFA19286 for ; Tue, 18 Apr 2023 16:59:50 +0200 (CEST) Received: from lana.proxmox.com (unknown [94.136.29.99]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Tue, 18 Apr 2023 16:59:49 +0200 (CEST) Received: by lana.proxmox.com (Postfix, from userid 10043) id D6B4A2C13AA; Tue, 18 Apr 2023 16:59:48 +0200 (CEST) From: Stefan Hanreich To: pbs-devel@lists.proxmox.com Date: Tue, 18 Apr 2023 16:59:44 +0200 Message-Id: <20230418145947.3003473-1-s.hanreich@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.430 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods 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 T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pbs-devel] [PATCH v4 proxmox-backup 0/3] add transfer-last parameter to pull/sync job 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, 18 Apr 2023 14:59:50 -0000 This patch series adds the possibility of specifying the transfer-last parameter for sync jobs / pull. This limits the amount of backups transferred. If specified, only the newest N backups will get transferred, instead of all new backups. This can be particularly useful in situations where the target PBS has less disk space than the source PBS. It can also be used to limit the amount of bandwidth used by the sync-job. Part of a series of changes that attempt to fix #3701 Changes from v3 -> v4: * Using two SkipInfos instead of one * Improve transfer-last parameter description * Further improved logging output * Move transfer-last input to advanced options Changes from v2 -> v3: * Add reason to SkipInfo * improved cutoff calculation * always re-sync latest snapshot, regardless of transfer-last * improved logging output Changes from v1 -> v2: * made condition for deciding which backups to skip clearer * changed type of transfer-last to usize instead of u64 * split api/ui changes into two commits proxmox-backup: Stefan Hanreich (3): partial fix #3701: sync job: pull: add transfer-last parameter sync job: pull: improve log output ui: sync job: add transfer-last parameter pbs-api-types/src/jobs.rs | 11 +++++ src/api2/config/sync.rs | 9 ++++ src/api2/pull.rs | 10 +++- src/bin/proxmox-backup-manager.rs | 11 ++++- src/server/pull.rs | 76 ++++++++++++++++++++++++------- www/config/SyncView.js | 9 +++- www/window/SyncJobEdit.js | 13 ++++++ 7 files changed, 119 insertions(+), 20 deletions(-) Summary over all repositories: 7 files changed, 119 insertions(+), 20 deletions(-) Generated by murpp v0.2.0 -- 2.30.2