Yes, I'm very sure I have no V3 backups anymore.
$Conf{PoolV3Enabled} is still enabled. I'll disable it soon.
$Conf{BackupPCNightlyPeriod} = 16, since 2 days. Before it was 1.
😁️
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.

One question: Is it really true that backuppc V4 still need the old ../*pool/?/ 
directories or only
until $Conf{PoolV3Enabled} is disabled?

Have a great day 😊️
Matthias

Am Samstag, dem 16.08.2025 um 16:49 +0100 schrieb G.W. Haywood:
> Hi there,
> 
> On Sat, 16 Aug 2025, [email protected] wrote:
> 
> > Hello 2all :)
> 
> :)
> 
> > After a lot of issues, mostly because of insufficient file limit (I
> > need ulimit -n 100000 ??)
> 
> Given 'a lot of issues' I'd be a little concerned that things might
> not be exactly as they should be in the pool.
> 
> > ... I've migrated all of my backups into V4. I have no more backups
> > in V3-style but still have files in V3 pool and cpool.
> > ...
> 
> First, are you sure that you've converted all your V3 backups to V4?
> If you still have backups which were made by BackupPC V3 and which
> have not been cnverted to V4 or expired (because of their age or for
> some other reason) then you still need them.
> 
> Do you still have $Conf{PoolV3Enabled} set to a true value?
> 
> In /etc/BackupPC/config.pl (or whatever your configuration file is),
> what value do you have for '$Conf{BackupPCNightlyPeriod}'?
> 
> Depending on the value of those options, after N nightly runs (where N
> is some power of two), BackupPCNightly should delete all your *unused*
> pool V3 files.  You shouldn't have to do it yourself.  Take a look at
> sub processPendingDeletes in BackupPCNightly, you'll see that it looks
> for files with only one hard link and deletes them.  There are one or
> two commented-out print statements in the file, you can uncomment them
> to try to get a bit more information, and maybe add a few of your own.
> 
> Incidentally I've noticed that there's a mistake in the documentation,
> which I quote below:
> 
> [quote]
>    Secondly, if you run BackupPC_migrateV3toV4 on all your backups, the
>    old V3 pool should be empty, except for old-style attrib files,
>    which should all have only one link since no backups should
>    reference them any longer. Before you turn off the V3 pool by
>    setting $Conf{PoolV3Enabled} to 0, make sure BackupPC_nightly has
>    run enough times (specifically, $Conf{PoolSizeNightlyUpdatePeriod}
>    times) so that the V3 pool can be emptied. You could do this
>    manually, but only if you are very careful to check that the
>    remaining files only have one link.
> [/quote
> 
> This references the value of $Conf{PoolSizeNightlyUpdatePeriod} and
> not $Conf{BackupPCNightlyPeriod}.  The latter is what determines how
> many times you need to run BackupPC_nightly to delete all the unused
> files.  It's on my TODO list.
> 
> > Are this hardlinks required from backuppc V4 or can I delete the
> > files in V3 pool and V3 cpool?
> 
> The thing which is bothering me is that your 'issues' might have left
> the pool in some inconsistent state.  I'd be reluctant to delete files
> without being sure they weren't needed, so I wouldn't delete anything
> manually - just use the tools which BackupPC provides.  You could stop
> BackupPC and run BackupPC_nightly by hand for example.
> 
> If you want to live dangerously you might for example stop BackupPC;
> rename the V3 pool and cpool directories and perhaps even make them
> unreadable for the backuppc user to be sure; create empty directories
> with the same names, ownerships and permissions; restart BackupPC;
> and then try to find out if you broke anything.
> 




_______________________________________________
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/

Reply via email to