I used the following command to initialize a repository:
duplicacy init Keith/Pictures /share/TR-004/Duplicacy/storage
The initial backup, which took a day, appears to have completed successfully. But neither the “list” command nor Duplicacy Web shows this repository.
There’s a snapshots/Keith/Pictures folder. Is this a bug? Is there a way to recover from this situation?
Yep, definitely sounds like there should be a sanity check for slashes (both forward and backward)…
Sadly, you can’t rename the snapshot directory, as the ID is saved and referenced in the encrypted snapshot file.
To fix your backup, and to avoid transferring it all again, initialise a new repository ID - maybe use a dash instead of the slash.
Before you do that, you may want to manually remove (or rename) the hidden .duplicacy at the root of your repository, so it’s able to create the new ID for the default storage.
When you run the new backup, it’ll seem like it’s doing it all over again, but should skip most chunks. You’ll end up with a new snapshot folder on the storage and you can manually delete snapshots/Keith/Pictures and run a cleanup with prune -exhaustive.
That worked, thanks. Do I need to report this as a bug?