On 5/23/21 3:50 AM, Josip Deanovic wrote: > > There is another option. > > Option 4: > --------- > If no valid full backup for the job could be found in the catalog, the > backup job will be upgraded from incremental or differential to full > backup. The message would be the same as the one described in option 1. > > This could happen if the job is prematurely pruned (before a new full > backup has been performed). >
Right, good point! And when a job (typically set to Level = Incremental) is first run, this will always happen too. :) Oh! And I just remembered that I had made an internal Bacula Enterprise feature request some time ago. It was accepted and implemented, so Option 1 is even better than I explained because now it tells you very clearly why there are "no prior suitable Full backups". Check this out: ----8<---- 23-May 08:12 speedy-dir JobId 6: The FileSet "Full Set" was modified on 2021-05-23 08:12:32, this is after the last successful backup on 2021-05-22 17:35:16. 23-May 08:12 speedy-dir JobId 6: No prior or suitable Full backup found in catalog for the current FileSet. Doing FULL backup. ----8<---- I am looking forward to Joe's feedback in this thread. :) Best regards, Bill -- Bill Arlofski w...@protonmail.com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
