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 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 > > 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? > > > > Regards > > Chris Wilkinson > > Hello Chris, > > I would recommend to remove the pool specification in the Schedule(s), and > instead use the "FullBackupPool", > "IncrementalBackupPool", and "DifferentialBackupPool" settings in your > Jobs/JobDefs. > > The "Pool" setting is required for a Job, so it must appear in the Job, a > JobDefs that the Job uses (if it uses one), or the > Schedule (if one is used). > > Additionally, if you use the three settings I mentioned above in your Job, > the Pool setting is still required, but will > always be ignored because one of the other three will automatically > override it depending on the Level of the job once the > job starts. > > > Hope this helps, > Bill > > -- > Bill Arlofski > w...@protonmail.com > > > > _______________________________________________ > 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
