Hi there,
On Wed, 8 Jul 2026, Matthias wrote:
...
BackupPC is reporting a wrong pool4 size:
2026-07-07 02:03:49 Finished admin (BackupPC_nightly -m -P 15 144 159)
If you have $Conf{PoolSizeNightlyUpdatePeriod} set greater than 1 then
the figure produced will only be an estimate. The documentation at
https://backuppc.github.io/backuppc/BackupPC.html#Configuration-Parameters
goes into this in detail.
...
The count of files is nearly correct. Just a delta of ~326.289 files. That is
1%??
But pool size is complete wrong. It should be 9102GB instead 2336.81GB
I know that I have files in pool which are not correct.
I have had regularly error messages in the log files regarding:
BackupPBackupPC_refCountUpdate: missing pool fileC_refCountUpdate: missing
pool file
The log message above is garbled in your email.
I tried to omit this messages by creating empty pool files with the name of
the missing files.
I'm not sure that doing things like this is wise. Rather than getting
too creative with your cures it might be more useful to you to do some
diagnosis. The configuration parametersand the logs can help a great
deal with that.
In the meantime I learned, this wasn't successfull because know I get error
messages in the log
files regarding:
BackupPC_refCountUpdate: ERROR pool file
/var/lib/backuppc/pool/92/90/9391966a5318da40fc690f27da3e1a25 has digest
d41d8cd98f00b204e9800998ecf8427e instead of 9391966a5318da40fc690f27da3e1a25
If you are suspicious of any particular pool files it might be better
just to delete them. BackupPC will replace them as necessary.
But can this incorrect files the reason for reporting a poolsize of
2336.81GB instead 9102GB ?
Perhaps - I don't know. There might be more information in the hosts'
individual logs about failed transfers, this may shed more light.
Be aware that $Conf{PoolSizeNightlyUpdatePeriod} defaults to a value
of 16. That is quite conservative on resource usage but it means that
it takes more than two weeks to traverse the entire pool to check that
the cached file sizes are correct - and of course in two weeks a lot
of files may have been added, deleted or changed, so it's only ever
going to be an estimate. Granted the estimate is usually nearer the
mark than seems to be your experience, but you do seem to have been
taking liberties with the pool of which I would never have dreamed.
How long does BackupPC_nightly take to run on your system? If it
doesn't take too long you could try {PoolSizeNightlyUpdatePeriod}=1,
or alternatively reducing it by one-half of its value at each backup,
to see if it gets the computed pool size closer to what you expect on
a timescale which might induce less frustration.
I'd be much more concerned that files are properly backed up than that
a few statistics might, frankly, be known to be bordering on guesswork.
--
73,
Ged.
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
