Hello,

testing one of the new 7.0.0 Features, mentioned in chapter 2.1.3 of the
great documentation:
»The Next Pool concept has been extended in Bacula version 7.0.0 to
allow you to specify the Next Pool directive in the Job resource as well.«

Job {
Name = CopyTest
Type = Copy
JobDefs = "GenericJobSettings" # see bacula-dir.conf
Client = client1-fd
Pool = quaterly-backups
Selection Type = Job
Selection Pattern = "CLIENT2-periodic B2D netshare-Gruppen-HR"
Next Pool = weekly-tapedup-buffer
}


*run
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
A job name must be specified.
The defined Job resources are:
…
15: CopyTest
…
Select Job resource (1-16): 15
Run Copy job
JobName: CopyTest
Bootstrap: *None*
Client: client1-fd
FileSet: None
Pool: quaterly-backups (From Job resource)
NextPool: LTO4-Archive (From Job's NextPool resource)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Here's some inconsistency. The source is claimed to be "From Job
resource", but the value actually is from Pool resource:

Pool {
Name = quaterly-backups
…
Next Pool = LTO4-Archive # needed for copy job
}


_run-directive-override works as expected:_

*run nextpool=weekly-tapedup-buffer
A job name must be specified.
The defined Job resources are:
…
15: CopyTest
…
Select Job resource (1-16): 15
Run Copy job
JobName: CopyTest
Bootstrap: *None*
Client: client1-fd
FileSet: None
Pool: quaterly-backups (From Job resource)
NextPool: weekly-tapedup-buffer (From Command input)

Thanks,

-Harry

signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users