Ah, soz. Yes, you don’t need those old .duplicacy directories with the new web UI…
Apart from the filters file that you may have manually created in there, they can easily be recreated* anyway - with your storage password etc. - if you need to go back to CLI. But, you can delete them.
If you run a regular prune job with the
-all flag, the snapshots for those old repositories will eventually get pruned as well, apart from the oldest one.
I’d just do that and wait until the day you end up with one snapshot for each old repository, then you’ll need to run a prune with option:
-id <old_repo_id> -r <last_revision> -exclusive to get rid of them, making sure no backups are running during this.
Finally, from what I can understand, your prunes won’t fully work for the next 7 days or so after you last did backups on those old repositories. This is because Duplicacy expects successful backups to occur on all repositories found in the storage between when fossils were collected and when they’re ultimately deleted.
After 7 days, those repos get ignored and ‘unblock’ prunes for the rest of the repos. The old repos still get pruned after time. See Prune (last paragraph). Just something to expect.
Edit: *unless you wanna keep the \logs?