The error in the topic title has been solved by running repair. So I am not directly asking for support in this. Rather, I am trying to figure out why this error seems to come up rather frequently. Because I think it shouldn’t happen. Since I just setup a new duplicati install (on Win 10), it’s pretty straight forward what I did:
After installing duplicati, it recognized an old database from a previous install. I deleted the database and changed the destination from Amazon Cloud to Backblaze B2 (completely new and empty B2 account). I also unselected all source folders except for a few which weighed about 9 GB. I also removed the amazon specific settings from the backup job and told it to go ahead and backup.
That was yesterday. I don’t think the backup completed yesterday before I shutdown the computer so when I turned it on this evening, it continued backing up. At that time it was not yet running as a service. I didnät logout the entire evening but I switched to another user and back.
When the backup completed (or perhaps it actually completed a second time, because the dashboard says “2 versions”), I turned off the tray icon and switched to duplicati as service. I then wanted to do a manual re-run and that’s when I got the error
Found 240 remote files that are not recorded in local storage, please run repair
Any ideas what might have caused those lost files and how it could be avoided in future? Couldn’t duplicati at least try a repair by itself instead of whining to the used?