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