Cleaning out Storage backend

[gotcode]

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?

[leerspace]

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:

Prune command details

The prune command has the task of deleting old/unwanted revisions and unused chunks from a storage. Click here for a list of related forum topics. Quick overview NAME: duplicacy prune - Prune snapshots by revision, tag, or retention policy USAGE: duplicacy prune [command options] OPTIONS: -id <snapshot id> delete snapshots with the specified id instead of the default one -all, -a match against all snapshot IDs -r <revision> [+] delet…