Haron:
Very similar problem. I also had another backup that I’d like to start from scratch. Name of the job is “VM”. Important: I have a number of similar jobs with prefixes like “VM X”, “VM Y”, “VM Z”. They are all keep backup files in the same folder!
Now when I try to re-create the task and recreate the database I can see only the error message: “Found 212 parse-able files (of 212 files) with different prefixes: VM X, VM Y, VM Z, did you forget to set the backup prefix?”
No, I did not forget to set the backup prefix, I imported the same old config.
I also tried to change prefix from “VM” to “VM Other”. Same result. It looks like Duplicati just don’t take prefix into account.
MacOS, Duplicati 2.0.2.1_beta_2017-08-01
Can you log into your destination and manually check for the expected pre-fixed files?
Note that changing the --prefix setting on an existing backup can cause as mentioned in this short topic - did you try running a Database Repair on any of these backups?
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 lo…