Further 6 month and the BPC on web is still reporting pool size 391GB,
while the disk df shows 767G occupied. I thought V3 backup will fade out,
and there are non at to moment according backupInfo, but the space is not
freed. Doing a "du" in the cpool (compressed pool):
cpool# du -sm *
18479 0
3091 00
3597 02
1186 04
1867 06
2170 08
1343 0a
3263 0c
2268 0e
30340 1
4479 10
1387 12
3202 14
3401 16
2097 18
2737 1a
1296 1c
2374 1e
19772 2
5607 20
...
reading the doc
https://manpages.debian.org/unstable/backuppc/backuppc.8.en.html#Storage_layout
made me think - those 0, 1, 2... etc subdirs in the pool are the old V3
direstories, because the V4 uses two digit subdirs..
So: Is it safe to delete the old V3 subdirs from cpool now, if there are
no V3 backups left?
I have $Conf{PoolV3Enabled} = '0';
Is it the reason why files were not "transfered" to V4 cpool?
Note: My pool is empty, all backups are compressed.
Adam Pribyl
On Mon, 30 Sep 2024, Adam Pribyl wrote:
After shrinking the FullMaxAge there were two days of backuppc "deletation",
but only 3% free space gain while "Prior to pooling and compression" size
decreased significantly, real space remained occupied.
There are now no V3 backups left as per
grep version /var/lib/backuppc/pc/*/*/backupInfo
5 days later, some 40GB are removed from "cpool4". I am still confused how
this works. At least the disk is not "full" now and backups are performed as
should, but there remains a big discrepancy between df/du reports and
backuppc (762GB vs 388GB). If it is occuied by v4 or v3 (undeleted?) backups
is not obvious to me and I am not sure how to find if there are any orpahned
files. I also did fsck - no issues.
Adam Pribyl
On Wed, 25 Sep 2024, Adam Pribyl wrote:
On Wed, 25 Sep 2024, Richard Shaw wrote:
On Wed, Sep 25, 2024 at 8:11 AM Adam Pribyl <pri...@lowlevel.cz> wrote:
2/2024 I did upgrade of debian to 12 with a new backuppc version 4. Now
after several month of further backups the backuppc reports a full disk.
This is from memory so take it for what it's worth...
The V3 pools are not converted to V4, over time the V3 backups expire
based
on your retention settings, so it looks like in your case having both is
taking up more room than you have.
As far as what to do about that other than potentially adding more disk
space temporarily I'm not sure there are a lot of good options.
Hm the cpool is 736GB by "df". Interesting enought I found the Schedule
setup is to do every 14 day a full backup and store 12 full backups, but
FullMaxAge is set to 365 days. Now there is 25 full backups oldest 365 days
old - it looks like the V3 backups are only expiring at FullMaxAge but are
not counted as regular full backups.. I tried to lower the FullMaxAge,
let's see what nigthly does. Thanks for the hint.
Thanks,
Richard
Adam Pribyl
_______________________________________________
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/
