Yes, that is what I have done now. I hadn't realised that pools specified
in the schedule override those in the job.
Best
Chris
On Wed, 16 Feb 2022, 4:37 pm Bill Arlofski via Bacula-users, <
bacula-users@lists.sourceforge.net> wrote:
> On 2/16/22 03:55, Chris Wilkinson wrote:
> > Is it possible
I have jobs set with priority 10 except for Catalog which is 11. I'll look
into mixed priority, thanks for the tip. I do get Catalog queued up when a
long job runs but it's not a problem.
Best
Chris
On Wed, 16 Feb 2022, 1:58 pm Gary R. Schmidt,
wrote:
> On 17/02/2022 00:18, Chris Wilkinson wrot
On 2/16/22 03: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?
>
> It doesn't seem like that is possible since the schedule resource requires to
> specify the pools that are used which would
> us
On 17/02/2022 00:18, Chris Wilkinson wrote:
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
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" Leve
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
require
