Backup always errors, rebuild won't work to clear the error, missing file

[JonMikelV]

@drakar2007

my hope would be that a successful backup run using --no-backend-verification would result in a ‘repaired’ file list / db

Unfortunately, the --no-backend-verification just disables the step that is throwing the errors, it doesn’t actually do anything to resolve it.

---

@ksignorini

I did a database delete and repair. Shouldn’t that grab the data from the backup location and rebuild based on that alone?

You are correct, a database repair alone should resolve such “files that are missing from the remote storage” type issues. I’m not really sure why it didn’t for you - and I know a few other people have reported this happening as well.

My guess is either:

1. The real error is something else but getting caught / reported as a “missing files” problem (thus a repair / recreate isn’t fixing something that isn’t broken)

2. There’s another issue on top of the “missing files” problem that causes the repair / recreate to not work correctly.

3. There’s an edge case bug in the repair / recreate process that isn’t being properly identified and handled.

---

@ksignorini

Delete operation failed for duplicati-b7707650f88a344d394eb83d08f2a7438.dblock.zip.aes with FileNotFound, listing contents,

I ran into this situation last month when doing some simulated failure recoveries. In my case a Repair (not recreate) was all that was needed to resolve that issue, though I did suggest a warning resulting from failing to delete a file that couldn’t be found is OK to show ONCE but the file should then be considered deleted.

Repeated "Delete operation failed" due to file not found

Let me start by saying I understand I should be able to resolve this issue by doing a database repair. I’m posting this because I think a repair should not be necessary and am hoping somebody can explain to me why it is. After changing my retention policy a bunch of destination files were cleaned up as they should be, however something went wrong when recording it in the local database. So now when the back runs it finishes just fine (so backups are working) but tosses out 48 sets of messages…

---

@drakar2007

i think you could create empty files that exactly match the “missing” names, upload them to your destination, and let the backup job delete them next time around

If @ksignorini is willing to test, it would be interesting to find out if this works. I’m torn on whether it will resolve the issue or move to a different set of warnings about the file sizes or dates being wrong.