I went ahead and changed my retention from 0:360 to keep 0:100 and did a prune, on the next check I got tons of missing chunk errors.
How should I proceed? What do I do?
Assuming the issue is due to prune not completing successfully (essentially deleting chunks but leaving ghost snapshots in the storage — these snapshots that were supposed to be deleted will be failing the check) I would run check with persist option, collect list of affected snapshots, and delete them from storage.
ok how do i run with the persist option? And also there are hundreds man, collecting a list and deleting them would be a daunting task to put it mildly.
Oh, I did not mean manually, more like parse output of check -persist (you can add -persist option to check so it continues after finding failure) either via script or, if this is a one-off, using some text editor (like BBedit) to extract list of bad revisions from a log file and then remove them all at once (the revision files under the snapshot subfolder under snapshots folder on the target).
Duplicacy should really have a heal command by now… or fix the bug with leaving stale snapshots in the storage. The latter is way better, safer, and easier.
2 Likes
Since you change the -keep 0:X retention period, you can probably assume all snapshots older than 100 days should have been removed…
Thus do a -list to determine which snapshot revisions are older than that date and manually delete them on the backup storage.
Its working hard on this been running for a while, can you tell me what “is already a fossil” means in the logs.
I see a few of these which I assume is a good thing “has been permanently removed” but mostly the above message.