[SOLVED] Traffic control method used - sync pull (side) jobs not limited?

[hvisage]

I'm busy syncing a mass number of snapshots to a new PBS, and it seems that the destination (that initiated the sync job) doesn't seem to apply the filter to the inbound traffic, but when I add this to the source, it does seem to apply and limit the outbound traffic.

I initially thought it was 'cause I've been using unprivileged LXC containers on the PVEs for PBS
(just need to do that backups quickly locally before I start to stream/sync the data offsite, so yes, I'm aware of why not to rely on the PBS in the PVE cluster)

So the questions started to arise:
- what is the mechanism(s) used by PBS to apply the traffic control?
- Should the PBS sync job's pulling (destination) side be able to limit on the inbound traffic?
(was using 0.0.0.0/0 and both sides, and only the source side seems to apply it on the outbound traffic)

Spoiler: destination - proxmox-backup-manager versions --verbose=true

root@pbs-mwp04:~# proxmox-backup-manager versions --verbose=true
proxmox-backup unknown running kernel: 5.13.19-2-pve
proxmox-backup-server 2.1.2-1 running version: 2.1.2
ifupdown2 3.1.0-1+pmx3
libjs-extjs 7.0.0-1
proxmox-backup-docs 2.1.2-1
proxmox-backup-client unknown
proxmox-mini-journalreader 1.2-1
proxmox-widget-toolkit 3.4-4
pve-xtermjs 4.12.0-1
smartmontools 7.2-1
zfsutils-linux 2.1.1-pve3

 

[dcsapak]

the global rate limit only concerns the api (so backups/restore/etc..) since a sync job only uses the api on the remote side this does not take effect
but with versino 2.1.1 you can configure a limit per sync job directly

 

[hvisage]

global rate limit only concerns the api

Ah ! Explains, thank you!

but with versino 2.1.1 you can configure a limit per sync job directly

Missed that :facepalm:

Thank you!