Cleaning out Storage backend

I have a Google Drive backend that has had a couple of installations of Duplicacy using it. While I was getting my home lab setup, I had to kill and reinstall the Duplicacy setup multiple times. Now I’m wondering if there are a bunch of “orphan files” from the old installations sitting in the storage backend taking up space.

Is there a way to tell which files in the storage backend are NOT from the current installation of Duplicacy?

If you’ve already deleted the unused snapshots under the snapshots directory in your storage, then you can use a prune to identify unreferenced chunks.

I think the appropriate command would be duplicacy prune -all -exhaustive -dry-run. If you wanted to actually remove the unreferenced chunks, then remove the -dry-run option.

Reference:

3 Likes