I’ve been looking at “The version(s) being updated to, already exists” because it was where your screenshot ended," This has never been reported before in the forum, and only once in GitHub issues (without answer), therefore this might take awhile (or not be possible by me). Finding the code is easy, but the whole flow isn’t.
You could try a couple of things to see if you can dodge issues to at least get your urgent restore finished…
You’re presumably in the Database option of your backup doing the repair. When trying “Direct restore”, the partial recreation might be noticed and cause a complaint like you got about the version already being there. Moving the broken database out of the way might possibly avoid that, and allow the “Direct restore” to work.
Are there any other versions of interest other than the one you had tried “Direct restore” on, if it got that far? Possibly you can restore something more-or-less-the-same as your ideal version, if that would help anything.
If you have another Linux system to install Duplicati, maybe it won’t get tripped up by whatever this one sees, which from the code looks like it already sees this version in the database (or maybe it sees a version twice). Are you seeing any duplication signs, for example in “Restore” offerings or in “dlist” files with the same time?
If need be, there are about two more levels of increasingly manual restore that you could try using if needed. Possibly one of them will be relaxed enough about the error checking, yet still sound enough to do a restore.
Recovering by using the Duplicati Recovery tool is one that’s not too hard, but does require download + disk.
If that won’t do it, it will at least have left a download of everything, then there’s a script that can do a restore.
With about four types of restore available, maybe one will work without getting tripped up on some problem…
I’m sorry things are not going well. The recreate algorithm is getting some rewrites, but I doubt you can wait…
