Hello,
The overrides, in my view, are a big mess with overrides and other
places where values can take precedence.
The problem is that it is such a big mess that changing anything is
likely to break someone's backups. If someone (not me) is willing to go
through the code and document all the different places that a particular
variable can be set, and then fixes *all* of them so that they are
reported in the Job log, and makes sure that anything entered via
bconsole takes precedence - then I would be happy to accept the patch.
Please note carefully, a big piece of the work is modifying the manual,
so this needs to be done as well for this to be accepted.
If someone wants to do a smaller manageable project, then simply
reporting at each place where a directive takes precedence over another
one in a different resource would already be a big help. At least the
user could then know why a variable is not what he expected.
Best regards,
Kern
On 08/14/2018 06:45 PM, Martin Simmons wrote:
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
------------------------------------------------------------------------------
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
