From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: [pbs-devel] applied-series: [PATCH v4 proxmox-backup 0/3] add transfer-last parameter to pull/sync job
Date: Tue, 25 Apr 2023 10:06:44 +0200 [thread overview]
Message-ID: <1682409983.e75c5v3xlp.astroid@yuna.none> (raw)
In-Reply-To: <20230418145947.3003473-1-s.hanreich@proxmox.com>
with the small Display follow-up we discussed off-list. thanks!
On April 18, 2023 4:59 pm, Stefan Hanreich wrote:
> 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
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
>
>
>
prev parent reply other threads:[~2023-04-25 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:59 [pbs-devel] " Stefan Hanreich
2023-04-18 14:59 ` [pbs-devel] [PATCH v4 proxmox-backup 1/3] partial fix #3701: sync job: pull: add transfer-last parameter Stefan Hanreich
2023-04-18 14:59 ` [pbs-devel] [PATCH v4 proxmox-backup 2/3] sync job: pull: improve log output Stefan Hanreich
2023-04-18 14:59 ` [pbs-devel] [PATCH v4 proxmox-backup 3/3] ui: sync job: add transfer-last parameter Stefan Hanreich
2023-04-25 8:06 ` Fabian Grünbichler [this message]
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=1682409983.e75c5v3xlp.astroid@yuna.none \
--to=f.gruenbichler@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