Hello again everyone, I've figured out what is happening to cause this issue.
Long story short, bacula pruned the file records from my last full backup job out of the catalog. It didn't prune the job itself, just the file records. This causes any file that hadn't been backed up since my initial full backup job to be considered as a new file to bacula when it does the incremental. Since most of my files don't change very often, that explains the behavior entirely.
There's plenty of warnings in the documentation about trying to restore from jobs that have had their file records pruned, but nothing about trying to do an incremental on top of a full that had it's files pruned. Obviously thinking about this a little bit would reveal that it's an issue.
Best Regards, Joe Zatarski _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
