On 6/12/25 9:24 AM, John Lockard wrote: >
I've seen this a couple of times, and haven't created a small job to test, but it appears that when I'm running a VirtualFull, and it fails for whatever reason, the next time a job for that FileSet runs it gets elevated to a Full and states that there is no previous Full.Is this a normal reaction to a Failed Virtual Full? Thanks, -John
Hello John,My first guess is that your original Full may have simply fallen out of its retention period, and it is just a coincidence that you get this backup level upgrade after a failed VFull. :)
A failed VFull does nothing to the original Full in the catalog, so this is strange. What is the exact message about the job being upgraded? Any chance the Fileset had been edited in this timeline too? If you are using a semi-recent version of Bacula, the job summary has some details about the last time a fileset was modified.I guess I am saying we will need some more information. :)
Best regards, Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
