Re: Limit Bandwidth of Incremental backups only

Bill Arlofski via Bacula-users <[email protected]>
Newsgroups gmane.comp.bacula.user
Message-ID <[email protected]>
Oops!  My previous message was accidentally sent before I even typed a character. :)

Here's the real reply...


On 2/27/25 10:53 AM, [email protected] wrote:
 >
> Bill Arlofski via Bacula-users wrote on 2/13/25 3:22 PM:
>> Here's an idea. 💡
>> In your Job, configure two RunScripts sections. One before and one after.
>> Have a small script that takes the current jobid and the level.
>> If the level is "limit", set bandwidth to xxxx, if the level is
>> "unlimited", set the bandwidth on the jobid to 0.
> 
> Yee boy now you're thinking!  I had no idea we could run scripts and
> send console commands, this is great.  Sorry for the late reply, I've
> been busy.  My final results and observations:

:)

I see from your comments/logs that "I missed it by that 🤏 much"™

https://www.youtube.com/watch?v=oPwrodxghrw  🤣


Yeah, I guess with a `RunsWhen = before`, we might not have the jobid/ujobid yet, but I thought we would/should...


> I'm not sure what you had another RunScript for "after" for, so left
> that out for now since the bandwidth_control script will set the
> bandwidth to unlimited for all non-Incremental jobs, what were your
> thoughts for including it?

I guess I was just thinking to set the client back to unlimited at the end of the job. OCD... Making sure to clean up, put 
things back where I found them.

But, as I think about this now, what if you run a job that sets the client to limited, then later in the day (or whenever, 
but before the next backup job runs) you need to do a restore. If the bandwidth limit applies to restores too*, you will be 
stuck with a slow restore.

*Note: This is a good question that I don't immediately know the answer to, but my first guess would be yes, but I am not sure.


> So far so good, though!
 > Great!


Yeah, this is good news!  Glad it works for you now!


> I noticed, though, in the beginning when the Accurate info is exchanged,
> that isn't limited by this mechanism, since I was watching the net
> meters on the client.  That was incoming data from the director it
> appeared (or storage).  Can that traffic be limited at all?  Once that
> was done several mins later, though, the client started uploading to the
> director, or storage technically i guess, steady at 100 k/s.  Thanks!

Yeah, the bandwidth limit does not affect/throttle this accurate info data transfer from the Director to the client.

I can't imagine this would be a big deal, but if it is something that is really adversely affecting your environment, you can 
always open a feature request. :)


Best regards,
Bill

-- 
Bill Arlofski
[email protected]

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
signature.asc (application/pgp-signature, 583 B)
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsCpBAEBCABdBYJnwQsdCZBIDTDab9XDQDUUAAAAAAAcABBzYWx0QG5vdGF0
aW9ucy5vcGVucGdwanMub3JnWV0Hbu67fNXURkMo1+2xVhYhBMuLnlBaSQiu
SUbb6UgNMNpv1cNAAABD0Qf+JDelvzcOARKDtWiXzcNZqGRARsTNV7YRpqG+
C54GxEHaCqU/txuoboShiDsb1tpBcfYBsvvyQ80wQzlrmxGm7m3Nw6Xh0tFP
ZFY6+n+SH07dlJjuBRRZRjJY/L6fBJlQv2BF6dlP43VVRaWd9V0cbLpHtyHY
u9q5Canwn5UoTLZnGRC0atz8DCMXsy3TEMRf2YzkFAI4wsVNsDx080qEqmob
of9wSL97ytg7BV456wQ0fKXzzX09CtEYYT9zY62cIxSGeg504RceYG7EsbbF
aZT77MR7vLTz93il/yoyHhlnKwFvMaJnxJWhV0saWG9+bF00AP9AwWvaZr5q
SziSAQ==
=2AzT
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.