This isn’t anything critical - I’m just playing around with learning Duplicati and found that changing
--prefix on an existing backup caused a
Found # files that are missing from the remote storage, and no files with the backup prefix My_Test , but found the following backup prefixes: duplicati.
This wasn’t too unexpected so I went ahead and renamed all my backup files to start with
My_Test instead of
duplicati and this time I ended up getting an
Found # remote files that are not recorded in local storage, please run repair error.
So I decided to run
repair via the
Commandline... GUI and got an error (which I’ve detailed here.
So my questions are:
- How stupid is it try and change
--prefixon an existing backup?
- Is it something that should be supported?
- If not, should a message be added to the parameter field warning people it’s not set up for already existing backups?
Oh - and speaking of the
--prefix field, I tried blanking the field and instead of the default
duplicati value returning (as I expected) the value
true appeared. So I guess that might be a legitimate “bug”.
Again, this is just me testing/playing so if this is all working as designed that’s a perfectly valid answer.