I think so too. Unfortunately it was put aside earlier because The database disk image is malformed.
Database disk image is malformed was one case where the damage was assessed then manually repaired, however that’s a rather advanced effort. Some Internet postings also say that an export then import can fix, however what was done at the link above was more. You could attempt an SQLite repair if you would like…
A relatively simple task would be to see if the damaged Duplicati-server.sqlite will open in an SQLite viewer. Information in the Backup table includes the given name for each backup, and the path to its job database. Information in the Source table includes the folders and files that had been chosen to go into each backup. There’s also schedule information and more, for your use as aids to manually rebuilding the configurations.
DB Browser for SQLite is a tool that you can install to see whether it can read the old Duplicati-server.sqlite.
The best case would be if you have exported and saved the backup configuration yourself. If so, just import.
Old databases with random names can be inspected by looking inside using Direct restore from backup files. Maybe your configuration is short enough to just recreate. For help, see above on old Duplicati-server.sqlite.