>>>>> On Wed, 8 Aug 2018 14:42:36 -0400, Phil Stracchino said: > > On 08/08/18 14:35, Martin Simmons wrote: > >>>>>> On Wed, 8 Aug 2018 13:13:19 -0400, Phil Stracchino said: > >> Er, correction, it's JobDefs that is overriding what I'm manually > >> selecting, not the Schedule. > >> > >> Specifically: > >> > >> Pool = Full-Tape > >> Full Backup Pool = Full-Tape > >> Differential Backup Pool = Diff-Disk > >> Incremental Backup Pool = Incr-Disk > >> > >> override whatever Pool and Storage I select when manually running a job. > > > > I agree -- I ended up moving all my pool overrides from the Job/JobDefs to > > the > > Schedule years ago to avoid this problem, but of course that causes tha > > different problem when manually running a job that gets upgraded. > > > > There could be two ways to fix this: > > > > 1) Override all pools using the pool parameter (and "Parameters to modify" > > setting). This will override even if the job is upgraded. > > > > 2) Add three more parameters (fullpool, differentialpool and > > incrementalpool) > > like in the Schedule resource to override the corresponding job parameters. > > This would be harder to use, but would DTRT if the job is upgraded. > > > > ...Or, just have manually specified parameters entered via the console > ALWAYS override Schedule or JobDefs. If the administrator says "Do this > specific thing", do the specific thing the administrator said to do.
Yes, that's what I meant by #1. AFAIK, pool is the only parameter that doesn't override (due to the multitude of related options in the job resource). __Martin ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
