[Bacula-users] Limit Bandwidth of Incremental backups only

[<sc...@ri...>]

Hi all,

    I'd like to use the Maximum Bandwidth directive, which can be
specified for a whole client, or per-job.  I'd like it to only apply to
incremental backup jobs though.  My idea was to split my job into two
jobs, one for full and differential backups and another for incremental
backups, and then split the schedule accordingly as well.

    Example config is below.  Previously, there was just one Job and one
Schedule defined.  The Job definition hasn't changed, but i modified its
schedule and removed incremental backups from it.  Then I copied the Job
definition to make a new Job with its own Name and Schedule, everything
else was the same, and added the bandwidth limitation.  Then created its
schedule for incremental backups only.

    The result however, is that bacula wants to get a full backup for
the incremental-only job anyway, due to "No prior or suitable Full
backup found in catalog."

    Why is that, when there is a full backup that already exists in the
Pool?  Is there something more I can do to link these two jobs, or is
the incremental job always going to want its own full backup?  There's
no way to limit the bandwidth like this, then?

Thanks

P.S. I sanitized the config below to try and make it generic, let me
know if I misnamed something or it otherwise doesn't make sense.

--

Job {
  Name = job
  Client = client-fd
  JobDefs = DefaultJob
  FileSet = clientFiles
  Schedule = jobSched
  Pool = client
  Storage = File-local
}
Job {
  Name = job-I
  Client = client-fd
  JobDefs = DefaultJob
  FileSet = clientFiles
  Schedule = jobSched-I
  Pool = client
  Storage = File-local
  Maximum Bandwidth = 100k/s
}
Schedule {
  Name = jobSched
  Run = Full jan 1st sun at 6:00
  Run = Differential 1st sun at 6:00
}
Schedule {
  Name = jobSched-I
  Run = Incremental mon-sun at 6:00
}