On 7/3/26 17:58, Phil Stracchino wrote:
Because your query does not distinguish between Full and Differential
jobs. If you want to store them separately, you need to select them
separately.
Hello.
I did as you suggested and it works.
Thanks.
BTW, I really need two different Jobs (one for Full and one for Diff),
since the "next pool" selection comes from the pool specified in the Job
(or, in case it's missing, from the JobDef).
So, suppose you have:
Job {
Name=CloudBackupFoo
Schedule=Weekly
Priority=10
JobDefs="DefaultJob"
FileSet=Foo
Type=Copy
Selection Type=SQLQuery
Selection Pattern="SELECT ..."
Storage=NAS
Pool=A
}
No matter where the SELECTed jobs comes from (e.g. pool B, C, etc...),
"next pool" is the one specified in pool A's definition.
This is strange and I wonder if that's a bug or if there's a reason I
cannot imagine behind this choice.
In any case, even if the SELECT clause picks jobs from different pools,
they are all going to the single "next pool".
Well, that's two jobs to monitor instead of one, but apart from that, it
works.
bye & Thanks
av.
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
