From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup v2 0/2] add transfer-last parameter to pull/sync job
Date: Wed, 11 Jan 2023 15:52:08 +0100 [thread overview]
Message-ID: <20230111145210.516392-1-s.hanreich@proxmox.com> (raw)
This patch series adds the possibility of specifying the transfer-last
parameter, limiting 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 patches that attempt to fix #3701
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
Stefan Hanreich (2):
partial fix #3701: sync/pull: add transfer-last parameter
ui: sync job: add transfer-last parameter to ui
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 | 17 ++++++++++++++++-
www/config/SyncView.js | 9 ++++++++-
www/window/SyncJobEdit.js | 13 +++++++++++++
7 files changed, 76 insertions(+), 4 deletions(-)
--
2.30.2
next reply other threads:[~2023-01-11 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 14:52 Stefan Hanreich [this message]
2023-01-11 14:52 ` [pbs-devel] [PATCH proxmox-backup v2 1/2] partial fix #3701: sync/pull: add transfer-last parameter Stefan Hanreich
2023-01-17 12:16 ` Fabian Grünbichler
2023-01-11 14:52 ` [pbs-devel] [PATCH proxmox-backup v2 2/2] ui: sync job: add transfer-last parameter to ui Stefan Hanreich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230111145210.516392-1-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox