I installed the new version 2.2.0.1 of Duplicati. It is not possible to restore files from local backups that were made with the old version. It gives an error message like: ”Missing Local Database” and the try to use the function to recreate the database ”Restore (delete and repair)” does almost nothing. It shows a message like that: ”File not fopund C:\Users\steph\AppData\Local\Duplicati\SFVETSFYJQ.sqlite”. Interestingly the restore works when switching to the old UI.
There are a few ways to start the restore process. Which of these best describe your setup?
- I have a backup configured and running, and I am restoring from that
- I have imported a backup configuration and am restoring from that
- I use the “Direct restore from backup files” option
- I use the “Restore from configuration” option
Hi @kenkendk ,
I have a backup configured with the previous version of Duplicati and running, and I am restoring from that with the new UI. The error does not occur when I switch to the old UI.
Hi @kenkendk ,
I found a possible problem. In my old backups, created with the old UI, I have parameter –dbpath set. The function “Recreate (delete and repair)” seems to recreate the DB in the folder specified by the parameter –dbpath. But the new UI does not check for this parameter and tries to find the database in path AppData\Local\Duplicati.
Hi, what is the solution for this problem? Have the same issue 
(I have imported a backup configuration file from an older version and try to restoring from that under a newer version)
When I restore the confuguration through the file I had to through the whole setting steps so im not sure, why there could be an issue with the dbpath 
I’m not certain there is such an issue. Did you recreate the local database too?
Import of configuration doesn’t do that. Let me quote from migration directions:
Backup configurations are available
Once the backup is re-created, it is required that you run the repair operation to make Duplicati recreate the local database for the backup.
(fixed the bad link in the copy from user docs)
Without a local database, very few things will work. Check the Database screen.
That also shows where the job database “should” show up when you recreate it.
BTW you can avoid going through all the job edit screens on import if you click:
but that doesn’t affect database placement, because that is on another screen.
If you would rather not recreate the database, old one can be copied into new,
assuming old version is still working. Use Database screen there to find its DB.
You can copy it in as its old name and set new GUI to it, or copy to new name.
If you’re only trying to restore (and never more) on new, then there is also this:
Direct restore from backup files
which makes a partial temporary database, but might be simpler in emergency.
The option --dbpath is listed as an advanced option, and it works, but the intention is that you only manipulate the database via the “Database” page. If you have set the advanced option, you will notice that it displays a different value than what --dbpath is set to. I recommend that you only use the “Database” page to change the path.
I tried creating a backup and set up the --dbpath to point to another location, and then I clicked the “Recreate” button, and I can see the issue. The new UI issues a “delete”, but this uses the path displayed on the page to delete the file, and if it fails, it will not continue.
If you click “Repair” instead, it will hit the inner runner which will replace the path shown on the database page with the one provider by --dbpath.
But I could not get anything to fail related to restore. Could you elaborate a bit on how I could reproduce this issue?
Could you post an error message or screenshots that explain what you are trying to do?
Ideally, we need to be able to follow the same steps and see the error for us to be able to fix it or provide workarounds.
If you just provide the error message, we can sometime guess what goes wrong, but a step-by-step explanation makes it a lot easier.
Hi @ts678 , to repair was the missing piece 
I thought with importing the configutation file everything would work (out of the box). Before the repair, when I choosed to restore the backup-selection-dropdown menu was empty and had no entries.
Thanks for the info to “save now”. Then I misunderstood the button because I thought it would make directly a now backup 
Hi @kenkendk Thanks for your reply.
To complete my error discription:
I used an older version of duplicati (I believe 2.0.1) and had a backup of the configuration.
After a new windows installation I switched to the newest version.
Then I imported the old configuration file and did go through save process again.
The error then was that the backup-restore-dropdown-menu was empty and didn’t show any errors.
I also “verified the data” from the context manu. What I didn’t try was to repair it because I thought something like that would be done automatically with the import. So it was only a misunderstanding on my side and after the tipp from ts678 now everything is working Thakns for all the help