Hi Bill and Kern,
Yes, it looks like Bill was correct. The jobs giving the problem were long
running jobs (12+ hours) so I think it just so happened that occasionally
(didn't happen every week), the full got pruned due to timing.
I increased "Max Full Interval" to 7 and things have been okay for
Hello Craig,
Given the first message below:
No prior or suitable Full backup found in catalog. Doing FULL
backup.
I would agree with Bill's first point. It appears that your Full
backup was pruned, so Bacula had to do another one.
Best regards,
Kern
On 03/31/2017 02:39 PM, Craig Shiroma wrote:
> Hi Bill,
>
> Hmmm, I know I didn't touch the fileset(s) and I have IgnoreFilesetChanges set
> to "yes" on these filesets. The FileSet date on one of the jobs is
> "2015-10-10 18:00:12".
>
> Here are some configs for one of the problem jobs:
> Pool {
>
Hi Bill,
Hmmm, I know I didn't touch the fileset(s) and I have IgnoreFilesetChanges
set to "yes" on these filesets. The FileSet date on one of the jobs is
"2015-10-10 18:00:12".
Here are some configs for one of the problem jobs:
Pool {
Name = server_shortname
Storage = server_shortname
On 03/31/2017 12:49 PM, Craig Shiroma wrote:
> Hello All,
>
> I have a few jobs that are on the below schedule:
>
> Schedule {
> Name = "WeeklyFullOnFriRunFirst"
> Run = Level=Full fri at 17:58
> Run = Level=Incremental sat-thu at 18:00
> }
>
> The jobs followed the schedule until last night
Hello All,
I have a few jobs that are on the below schedule:
Schedule {
Name = "WeeklyFullOnFriRunFirst"
Run = Level=Full fri at 17:58
Run = Level=Incremental sat-thu at 18:00
}
The jobs followed the schedule until last night which was a Thursday. An
incremental was suppose to run, but a
