I tried a schedule like so to test this out by deleting the Pool= part.
Schedule {
Name = "archive"
# Run = Pool="archive-full" Level="Full" 1st sun at 4:00
Run = Level="Full" 1st sun at 4:00
Run = Pool="archive-diff" Level="Differential" 2nd-5th sun at 4:00
Run = Pool="archive-incr" Level="Incremental" mon-sat at 4:00
}
This works fine. I had thought that the pool= was necessary but had misread the
docs and not appreciated the order of precedence of pool defs in job and
schedule resources.
Using the first version of the schedule resource in 2 jobs leads one of the
jobs to use the pool specified in the schedule rather than the one defined in
the job and hence the wrong volumes get written.
Best
-Chris-
> On 16 Feb 2022, at 11:15, Josip Deanovic <djosip+n...@linuxpages.net> wrote:
>
> On 2022-02-16 11:55, Chris Wilkinson wrote:
>> Is it possible to define two jobs to use the same schedule resource, i.e.
>> have two jobs to run using the same schedule?
>
> Hi Chris,
>
> Yes, it's possible and it's a common thing.
>
>> It doesn't seem like that is possible since the schedule resource requires
>> to specify the pools that are used which would usually be different. I
>> wonder if there is a logical reason for requiring schedules to define the
>> pools used when this info is already in the job resource?
>
> Definition of a Schedule resource doesn't require pool to be specified.
> Multiple jobs can use the same pool. This is also a common thing.
>
>
> Regards!
>
> --
> Josip Deanovic
>
>
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
