Hello,
I use restic 0.8.1 with rest-server as backup destination.
I try to recover backup, which wasn’t completed due lack of space on destination. I had to unlock the destination, rebuild-index and start new backup, this seems be working quite correct. Only the first backup after repository fix runned much longer than regular backups.
Now I try to run prune to remove unneeded files (I didn’t use the forget) and it says:
repository contains 954787 packs (8928751 blobs) with 4.076 TiB
processed 8928751 blobs: 4521593 duplicate blobs, 2.121 TiB duplicate
load all snapshots
find data that is still in use for 26 snapshots
[6:40] 100.00% 26 / 26 snapshots
found 4398972 of 8928751 data blobs still in use, removing 4529779 blobs
will remove 0 invalid files
will delete 1 packs and rewrite 923625 packs, this frees 2.125 TiB
but after performing about 10% of the prune I see, that it is eating more and more space, about 400GB for the 10% of prune. Is it expected, that the command need in fact double the storage needed for backup? It looks like the prune will copy all data to the new blobs and then remove the old ones?
I am also performing the maintenance (rebuild-index, prune) locally on backup server with rest-server process stopped. I hope this isn’t any problem.