Martin, excellent advice. it says at the job info:
level=Data
then under the schedule info:
Run Level=Full
..
Run Level=Incremental
..
Run Level=Incremental
according to the schedule it is Incremental
The precedence of which level is used cannot be derived from the "show job"
alone.
I was assuming that the job level declared within the job or jobdef would be
overriding levels declared elsewhere. The manual albeit explains that the level
declared in the schedule takes precedence. For me this is a bit unfortunate, as
I then need an own set of schedules for backup jobs with runs for Full and
Incremental, and another set for verify jobs with a run for level=Data and
possibly additional runs for other verify levels. considering the number of
schedules I have defined for use this would be a lot.
Do you see a more elegant solution?
I guess it wouldn’t work if I added a run for level=Data to all of my
schedules, as Bacula wouldn’t know how to match the runs with the correct level
to the fitting job type? Or would the Director know that runs with level=Data
only apply to jobs with type=Verify, and levels Full and Incremental apply to
backup, migrate and copy jobs?
Cheers,
J/C
> On 5. Sep 2022, at 17:47, Martin Simmons <mar...@lispworks.com> wrote:
>
> Maybe the output of
>
> show job=job1-verify
>
> will show where the level is being set to Incremental? It might be the
> Schedule resource for example.
>
> __Martin
>
>
>>>>>> On Sat, 3 Sep 2022 22:13:16 +0200, Justin Case said:
>>
>> Hi
>>
>> I am confused why I am getting this error:
>>
>>
>> 03-Sep 22:00 bacula-dir JobId 2481: Fatal error: verify.c:73 Unimplemented
>> Verify level 73(I)
>> 03-Sep 22:00 bacula-dir JobId 2481: Error: Bacula bacula-dir 11.0.6
>> (10Mar22):
>>
>> —snip—
>>
>> Verify Level: Incremental
>> Verify JobId: 0
>> Files Examined: 0
>> Non-fatal FD errors: 1
>> FD termination status:
>> Termination: *** Verify Error ***
>>
>> The Verify Level shown above is definitely wrong, here is the definition
>> (and it sets Data as Level!)(I removed the schedule resource name):
>>
>> Job {
>> Name = “job1-verify"
>> Level = "Data"
>> Pool = “pool1"
>> FullBackupPool = “pool1"
>> IncrementalBackupPool = “pool2"
>> Fileset = “users"
>> VerifyJob = “job1"
>> JobDefs = “jdef1-verify"
>> Enabled = yes
>> AllowIncompleteJobs = no
>> AllowDuplicateJobs = no
>> }
>> JobDefs {
>> Name = “jdef1-verify"
>> Type = "Verify"
>> Level = "Data"
>> Messages = "Standard"
>> Storage = “storage1"
>> Pool = "Default"
>> Client = “client-fd"
>> Fileset = "EmptyFileset"
>> WriteBootstrap = "/bootstrap/%c_%n.bsr"
>> Priority = 40
>> }
>>
>> Any ideas?
>>
>> Thanks for your time,
>> J/C
>>
>>
>>
>>
>> _______________________________________________
>> 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
