You may want to check what the joblog contain. All my AI job are showing the files backup'ed when there's some, and also all my volumes show me jobid stored on.
Are you sure you didn't get caught by the fact that after consolidation, history is rewritten, and older jobid get new files in due to the consolidation ? On Wednesday, 18 March 2026 at 11:27:35 UTC+1 Patrick Hasler wrote: > Hi Bruno, > > Thank you for the quick reply! The list is actually empty: > *list files jobid=93451 > * > > I tried it for mutiple jobids. For older job with the regular file size > the command is working as expected and I get a list of files. > > > > > On Wednesday, 18 March 2026 at 11:17:18 UTC+1 Bruno Friedmann > (bruno-at-bareos) wrote: > >> You can see what files have been backup'ed by using >> bconsole >> list files jobid=12345 >> >> On Wednesday, 18 March 2026 at 10:16:57 UTC+1 Patrick Hasler wrote: >> >>> We noticed a quiet urgent issue on some of our larger systems where we >>> do backup for with Bareos. Suddenly every new incremental backup is huge >>> and also ruffly has the same size every time (See screenshots below). >>> Usually I would suspect something changing on the system (For example a >>> DB backup dump cronjob) but as this affects multiple completely unrelated >>> systems, this can be ruled out. There is no indication of any kind of large >>> file changes on all the affected hosts, so the question is: What is Bareos >>> actually backing up here? >>> >>> If I go to the restore section to check what files were actually backed >>> up by the job, the "File selection" section just stays empty, so we don't >>> have any idea what's in the backups. Due to there huge size we also cannot >>> just restore them to the client to check their content and as we use >>> encryption we cannot simply extract the data from the volumes on the >>> Storage Daemon's side. >>> >>> There was no recent Bareos software upgrade, so I don't think that this >>> is a new software bug. Also the affected clients use different versions of >>> the File Daemon (24.0.7, 25.0.2), while the Director and Storage Daemon >>> both use 25.0.2. >>> >>> What could be an explanation for this kind of behavior? I mentioned >>> Always Incremental because I'm pretty sure that the problem is somehow >>> related to it as the new huge incrementals started showing up after the >>> most recent VirtualFull. But this is not the first VirtualFull, so I'm not >>> sure why this behavior suddenly started.[image: >>> bareos_huge_incrementals-1.png] >>> >>> [image: bareos_huge_incrementals-2.png] >>> >> -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bareos-users/d62b30c1-d83e-454e-b6b5-1f522613907en%40googlegroups.com.
