Thanks for looking deeper. I agree that these missing pool file warnings are ominous news for recovery. The link you referenced ( https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg33090.html) indicates to me also that in v4, the missing pool file message is not benign.
It will take me at least a few days to run a full recovery analysis to see if there are file recovery issues. Do you know how to get the file/backup#/host from a pool file reference that was reported missing in the log? That detail would certainly help speed up my analysis and potential recovery. I’ll update once that’s done and have some actionable data. Sam On Sun, Dec 10, 2023 at 9:18 PM <backu...@kosowsky.org> wrote: > G.W. Haywood wrote at about 13:32:42 +0000 on Sunday, December 10, 2023: > > Hi there, > > > > On Sun, 10 Dec 2023, Samual Flossie wrote: > > > > > The server log has a bunch (17k) of "BackupPC_refCountUpdate: missing > pool > > > file" messages. Reread the v4 docs, github wiki, issues and a bunch of > > > messages on this email listserve. > > > > > > I am correct that these messages are benign and do not indicate that a > > > backed up file is missing a pool file? > > > > I believe you are correct. > That is true for v3.x but for v4.x if the pool file is missing it may > very well represent the (only) copy of data for the same file that is > backed > up across multiple machines and backups. > > > > > My overriding concern is that a file will not be able to recover > > > when needed and that issue was signaled by a benign log message. > > > > I'm sure that you are right to be concerned. I would be. > > > > > What additional steps should be taken to resolve these > > > "BackupPC_refCountUpdate" messages? > > > > Does this help? It's just one result from a quick search. > > > > > https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg33090.html > > > > It seems that this issue has cropped up before without an obvious > > cause, but there was a suggestion that an unclean server shutdown > > might have been implicated. I think that's just a guess. > > That is my sense and was the best explanation for when I had some such > errors a few years ago. > > > > Full marks, incidentally, for looking at your server logs. :) > > > > -- > > > > 73, > > Ged. > > > > > > _______________________________________________ > > BackupPC-users mailing list > > BackupPC-users@lists.sourceforge.net > > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > > Wiki: https://github.com/backuppc/backuppc/wiki > > Project: https://backuppc.github.io/backuppc/ > > > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ >
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
