[SOLVED] PUSH SYNC Limit no works

[supermicro_server]

Hello everyone,
I've setted up a PUSH sync job at 10MiB/s but this limit doesen't work as aspected.
On the both firewall interfacess graph and zabbix monitoring I have the evidance that the sync job went at more del 200Mbps.
I would have expected more or less 100Mbps.
Has this happened to anyone before?

thank you
Regards

 

[Chris]

Hi,

I've setted up a PUSH sync job at 10MiB/s but this limit doesen't work as aspected.

at which side did you set up the rate limit? The sync source or the sync target? Have you also configured burst rates?

 

[supermicro_server]

Hi,

at which side did you set up the rate limit? The sync source or the sync target? Have you also configured burst rates?

Hi Chris,
I setted up the rate limit at source (PUSH) site, where I have the datastore and the PUSH job.
Since I have PUSH job and sync source, I'm not sure to figure out what "sync target" means .
Where can I set "burst rates"?
Thank you!

 

[Chris]

Hi Chris,
I setted up the rate limit at source (PUSH) site, where I have the datastore and the PUSH job.
Since I have PUSH job and sync source, I'm not sure to figure out what "sync target" means .

With sync target I'm referring to the PBS host receiving your backup snapshots, so your remote host.

Where can I set "burst rates"?

The burst can be set in the same traffic control edit window, see https://pbs.proxmox.com/docs/network-management.html#traffic-control

 

[supermicro_server]

With sync target I'm referring to the PBS host receiving your backup snapshots, so your remote host.

The burst can be set in the same traffic control edit window, see https://pbs.proxmox.com/docs/network-management.html#traffic-control

As far as I know, I you cannot limit a sync job by using the traffic controll.
The traffic controll is only used to limit PVE<-->PBE backup jobs. In the documentation I can see this note:
Note:
Sync jobs on the server are not affected by the configured rate-in limits. If you want to limit the incoming traffic that a pull-based sync job generates, you need to setup a job-specific rate-in limit. See Sync Jobs.

but anyway, you are saying me that I have to set:
1) Rate limit on the PUSH job
2) Traffic limit on the destination (Burst in)

is it correct?

Thank you

 

[Chris]

No, what I meant is that since the PBS sync job acts like a backup job for the remote target, you can set the rate limit on the target PBS instance. The burst was just out of interest in case you had a value that would allow for an initially higher throughput.

 

[supermicro_server]

No, what I meant is that since the PBS sync job acts like a backup job for the remote target, you can set the rate limit on the target PBS instance. The burst was just out of interest in case you had a value that would allow for an initially higher throughput.

ok Chris, thank you.

I could define some rules to apply the rule only to incoming remote PBS traffic, correct?


Since the Rate Limit on the push job is not working, can I consider it a bug?

thank you

 

[Chris]

I could define some rules to apply the rule only to incoming remote PBS traffic, correct?

Yes, that is what I intended with setting the rate limit on the target PBS. That is a valid workaround to apply the rate limit (if you have access to the remote).

Since the Rate Limit on the push job is not working, can I consider it a bug?

Had a glance at the code now: This is indeed a bug, although it is limited to the WebUI. Will send a patch to fix this asap. For the time being, the rate limit for the sync job in push direction can also be set on the source PBS by e.g.

proxmox-backup-manager sync-job update ID --rate-out 20MiB

Note that this is the same as for the pull, but rate-out has to be set instead of rate-in

 

[Chris]

For reference: https://lore.proxmox.com/pbs-devel/20250310170125.528732-1-c.ebner@proxmox.com/T/

 

[supermicro_server]

For reference: https://lore.proxmox.com/pbs-devel/20250310170125.528732-1-c.ebner@proxmox.com/T/

Thank you Chris!