Vicious circle when restoring a database:

Situation:

  1. All backup-versions were restorable,
    except the last backup-version which was incomplete maybe corrupted
  2. Creating new backups was impossible

That’s why I tried to repair the local database.

C:\Users\Marti\AppData\Local\Duplicati\NNHHVJPPQQ.sqlit

Using the web interface.

But this failed with the error-message

“Recreated database has missing blocks and 12 broken filelists.
Consider using “list-broken-files” and “purge-broken-files”
to purge broken data from the remote store and the database.

When I tried to fix this using CLI:

.\Duplicati.CommandLine.exe list-broken-files "webdavs://webdav ….

Then I got the error-message

Database file does not exist: C:\Users\Marti\AppData\Local\Duplicati\OKRWXCLNFR.sqlite

So, I came to the conclusion:

1. It should be possible to restore all Backups except the last backup solely from the remote files.
2. All data, but the data of the last data backup is remote available.
3. To rebuilt the database, I need a database which I never had; I thought, the remote-data should be enough

Welcome to the forum @Martin1

Usually it’s easier and safer to use Commandline option of the GUI, as older docs describe.

Using the Command line tools from within the Graphical User Interface

If an equivelent section is in the new docs, I didn’t find it, and suggest it be more prominent.

Command Line Interface CLI

Each command also requires the option --dbpath=<path to local database>, but if this is not supplied, Duplicati will use a shared JSON file in the settings folder to keep track of which database belongs to each backup. Since there is no state given, the remote url is used as a key, because it is expected to uniquely identify each backup. If no entry is found, a new entry will be created and subsequent operations will use that database.

Your use is showing signs of assigning (but not yet creating) a new database. Check both paths:

(probably with last character omitted, but distinctly different from the missing database error)

Ideally remote data works well. Here it didn’t, probably left a database needing fix (look for it), but omitting dbpath to say where the database needing fix is led it astray. Try either dbpath or GUI.

after investing plenty days I gave up; archived the backup-files and started a new backup-History.