On 10/7/25 6:42 PM, Phil Stracchino wrote:
On 10/7/25 12:02, Andreas Koch wrote:
Hi all,
I have a set of related Jobs (multiple clients + always a single Catalog)
that are scheduled together and always run in sequence. I would like to
force each of these related job sequences to be written to its own tape
volume.
Currently, I achieve this by setting the MaxVolumeJobs for each tape in
that pool to the exact number of jobs for each of these runs. Afterward,
that volume is marked full and the next job sequence is written to a
different tape. That has served me well thus far.
However, recently, I see greater fluctuations in our number of clients (and
their associated jobs). Thus, my initial approach has become unwieldy, as I
would need to manually update MaxVolumeJobs every time the number of
clients changes.
Is there a better way to achieve my goal that can deal more robustly with
varying numbers of clients? Something like UseVolumeOnce, but not applying
to individual jobs but only after the Catalog job is complete ... ?
Would VolumeUseDuration work for you? That's what I do: 'Volume Use
Duration = 23h'
Unlimited Jobs are allowed in a single Volume, but 23h after creation, that
Volume is DONE, no new Jobs can be added to it, and the next day's Jobs have
to get a new Volume.
That is a more robust duration than my current approach, thank you! I will
have to use a longer duration than 23h for our backups, though :-)
Many thanks,
Andreas
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
