Re: [Bacula-users] Jobs don't remain on schedule

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 2 weeks now.

Thank you for the help guys!

-craig

On Sat, Apr 1, 2017 at 5:21 AM, Kern Sibbald <kern AT sibbald DOT com> wrote:

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 08: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 which was a Thursday. An incremental was suppose to run, but a Full was run instead. Would anyone know what could cause this to happen? Previous full backup did run on a Friday at 17:58.

The log for these jobs show similar text shown below:

bacula-dir JobId 413490:

bacula-dir JobId 413490: No prior or suitable Full backup found in catalog. Doing FULL backup.

bacula-dir JobId 413490: Start Backup JobId 413490, Job=servername.2017-03-30_18.00.06_05

bacula-dir JobId 413490: Max configured use duration=82,800 sec. exceeded. Marking Volume "servername-258519-vol" as Used.

bacula-dir JobId 413490: Pruning oldest volume "servername-263826-vol"

bacula-dir JobId 413490: There are no more Jobs associated with Volume "servername-263826-vol". Marking it purged.

bacula-dir JobId 413490: All records pruned from Volume "servername-263826-vol"; marking it "Purged"

bacula-dir JobId 413490: Using Device "servername" to write.

bacula-sd JobId 413490: Recycled volume "servername-263826-vol" on file device "servername" (/backup01/servername/), all previous data lost.

Seems like something is out of sync with the schedule that is causing the Full to run on the wrong day.

Best regards,

Craig

------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

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