Hi there,
On Sun, 17 Aug 2025, matth...@gmx.at wrote:
Yes, I'm very sure I have no V3 backups anymore.
$Conf{PoolV3Enabled} is still enabled. I'll disable it soon.
When you do that, the only change to operation should be that BackupPC
V4 will no longer look for anything in the V3 pool.
$Conf{BackupPCNightlyPeriod} = 16, since 2 days. Before it was 1.
Am I right in thinking that BackupPC has been running with the value
set to 1 for some days after you converted all your V3 backups to V4?
Yesterday I've already deleted in ../*pool/?/:
1. all files with only 1 hardlink
2. all files which are only hardlinked with other files in pool or cpool
I didn't remove any file in ../*pool/??/ and I still have a list of all (2)
deleted files and where
they was linked too. So I'm able to restore any of them.
Now I don't have a single file left in ../*pool/?/??
Tonight BackupPC_nightly run and have no errors.
:)
Just 1.800 "admin : BackupPC_refCountUpdate: missing pool file". But this only
affects files that
are a few years old. I'm still investigating.
Have you tried BackupPC_fsck?
This might (possibly) help:
https://sourceforge.net/p/backuppc/mailman/message/58712645/
See also 'Extensions and Scripts' in the Wiki:
https://github.com/backuppc/backuppc/wiki/
One question: Is it really true that backuppc V4 still need the old ../*pool/?/
directories or only
until $Conf{PoolV3Enabled} is disabled?
If $Conf{PoolV3Enabled} is set to a true value, BackupPC version 4
uses the files in the V3 pool if it needs to. If you *successfully*
converted all the V3 backups to V4 backups, then after the requisite
number of executions of BackupPC_nightly (this number depends on the
value of $Conf{BackupPCNightlyPeriod}) then theoretically it should
have deleted the V3 pool files by itself and it will no longer need
anything from the V3 pool. The only files that should remain in the
V3 pool are *singly-linked* attrib files, which you can delete if you
wish because they are not used if they only have a single link but the
documentation is clear that you need to check carefully. Also in this
situation, you can set $Conf{PoolV3Enabled} to false (whether you have
deleted the V3 attrib files or not).
The script which converts V3 backups to the V4 equivalent has not had
anything like as much exercise as it could have had. In circumstances
where there are 'issues' it could conceivably fail to do what it is
intended to do (and perhaps do things which it is not intended to do).
In such a case you probably do not want to set $Conf{PoolV3Enabled} to
a false value until you have made sure that no V3 pool file is needed.
At this late stage in the life of BackupPC V3 I think in the future it
is likely that very few people will want to migrate V3 systems to V4.
So it's unlikely that the conversion script will ever benefit from the
sort of extensive testing which it would need to make it bullet-proof.
It seems likely that your conversion of V3 backups to V4 backups did
not go very well. You said that there were 'issues', and that now the
count of missing pool files is nearly two thousand. (1.800 - is that
right? in the UK we use comma , not decimal point . as the thousands
separator). You are right to want to investigate. Are you able to
recover a few files successfully? Perhaps choose some at random, and
some because they're big/small/valuable/new/old?
Have a great day
U2. :)
--
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/
