Original post looks like it’s building a new database. Other posts lack details.
So far, the most damage using an old database has caused is error like this:
Restore started at 11/13/2025 12:27:15 PM
Checking remote backup ...
Listing remote folder ...
Extra unknown file: duplicati-20251113T172656Z.dlist.zip
Found 1 remote files that are not recorded in local storage. This can be caused by having two backups sharing a destination folder which is not supported. It can also be caused by restoring an old database. If you are certain that only one backup uses the folder and you have the most updated version of the database, you can use repair to delete the unknown files.
The operation Restore has failed => Found 1 remote files that are not recorded in local storage. This can be caused by having two backups sharing a destination folder which is not supported. It can also be caused by restoring an old database. If you are certain that only one backup uses the folder and you have the most updated version of the database, you can use repair to delete the unknown files.
ErrorID: ExtraRemoteFiles
Found 1 remote files that are not recorded in local storage. This can be caused by having two backups sharing a destination folder which is not supported. It can also be caused by restoring an old database. If you are certain that only one backup uses the folder and you have the most updated version of the database, you can use repair to delete the unknown files.
Restore seems to be NOT using the dbconfig.json file if it isn’t there. Possibly
temporary file is used, as I see dup- files used looking suspiciously SQLite…
If file IS there, one doesn’t get things like dindex files downloading to build DB.
That sort of detail should be provided on any report. Also look in dbconfig.json.
Possibly the developer will say more, but let’s supply whatever info is available.