Not sure what this part means. The recovery tool builds a crude map of the remote contents.
It specifically does not build a database, in an attempt to keep the process as simple as possible, with the expectation that less code == fewer places things can break.
If your goal is to restore files, the recovery tool is designed to be able to do so without the local database.
If your goal is to continue running the backup, you need the database rebuilt.
Fair point. I think we should allow the process to continue.
I am certainly not objective in that, but it depends on what you need. There is a big comparison here. And some more in the Comparison category.
Do you have any idea on what might have created this? We changed the default from 100KiB to 1 MiB for 2.0.8.1, but any operation will first verify that the size is correct.
Not really, since you have a mix of sizes in there. Any version of Duplicati will complain if this is not correct.
We are currently investigating the recreate process and have identified some slowdowns related to the SQLite database once the tables are sufficiently large. I am hoping that we will soon (read: a few weeks) have a more performant recreate process.
I have noted your request to also be able to continue the recreate process.
Any updates? 