Hi Bill

The NextPool Directive actually is set to the equivalent of t2-pool-full. What 
you found was just a mistake I made during redacting the config for the posting.

Please note that in the JobDef and in the Job resource the is no job name 
mentioned, i.e. the copy jobs are identifying the jobs to be copied merely by 
means of the pool name. if I would remove  FullBackupPool and 
IncrementalBackupPool then there would only be a reference to t1-pool-full in 
the jobdef, so when would the incremental jobs be copied? (reminder: I use 
different pools for full and for incremental). I would assume that I then need 
an additional copy job for the pool with the incremental jobs?

If the Level of the copy job does not mean anything how come, that the director 
is planning to copy incremental jobs when the schedule says that the Level 
override is Incremental? Sounds weird to me as a beginner with Bacula.

I also have a number of other copy jobs, where each job has a pool for full 
backups and a pool for incremental backups. In that case we have always the 
same FD and fileset per job. And there the scheduling works, it copies 
incremental jobs on the days where the schedule says so and full jobs ob the 
days where the schedule says that.

Best,
 J/C


> On 14. Sep 2022, at 17:51, Bill Arlofski via Bacula-users 
> <bacula-users@lists.sourceforge.net> wrote:
> 
> On 9/14/22 07:08, Justin Case wrote:
> 
> Hello Justin,
> 
> 
> I noticed that your t1-pool-full has a wrong NextPool defined. It is pointing 
> to itself:
>> Pool {
>>   Name = “t1-pool-full"
>>   PoolType = "Backup"
>>   LabelFormat = “t1-full-"
>>   ActionOnPurge = "Truncate"
>>   MaximumVolumes = 100
>>   MaximumVolumeJobs = 1
>>   MaximumVolumeBytes = 50000000000
>>   VolumeRetention = 6048000
>>   NextPool = “t1-pool-full"            <---- Should be t2-pool-full, right?
>>   Storage = "t1-storage"
>>   AutoPrune = no
>>   Catalog = "MyCatalog”
>> }
> 
> 
> Additionally, I would remove the FullBackupPool and IncrementalBackupPool 
> settings from the mycopyjob JobDefs.
> 
> 
> That is a starting point I would say.
> 
> Then, if you are still having issues, please re-post logs and adjusted 
> configs.
> 
> 
> Additionally, the Job's Level for Copy jobs does not mean anything. In my 
> environments, I set all Copy/Migration jobs' Level=Differential since I don't 
> use Differentials, and this just gives me another indication that the job is 
> a copy or Migration job. ymmv.
> 
> 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

Reply via email to