I would love to figure out how to get into the deadlock state, but I don’t think I can get more information than what you already shared in terms of bugreports.
Summing up…
The backups in question are running again without any apparent issues.
While this was - hopefully - a relatively rare situation, I thought I would still provide a summary of the steps taken.
Situation - move from old laptop to a new laptop, with a failure of the new laptop a month later. Fortunately, I still had a full copy of the prior laptop from before the move. So I was able to move back to the old laptop, and just needed to restore data from the prior month. There were no issues with getting the Duplicati backup config back on the old laptop and I was able to restore the data by performing a “direct restore” from the cloud backups (on b2).
The issue was then getting the local database back in usable shape.
- “repair/recreate” database. This took 2.5 days and apparently downloaded all the backup data from b2.
- “list”. This showed all of the expected filesets.
- “list-broken-files”. This showed broken files in 3 filesets.
- “delete” against each of the 3 filesets. The filesets were deleted, but left things in a deadlock state where commands would fail indicating I needed to run “repair”, while “repair” would indicate there was no need for repair.
- As per recommendations here, upgraded to Canary 2.1.0.112, deleted the local database, and re-ran “repair/recreate”. This only took a few hours and unlike the prior recreate it apparently did not download all the backup data from b2.
- At this point everything seems to be OK.