I installed 2.2.0 today - in the process, I deleted and recreated the local sqlite db for each backup job.
Now I can’t delete the original sqlite db files.
Troubleshooting:
I don’t think there are any active processes that would lock these files…
Any thoughts?
It would be best to look. You can start Task Manager as Administrator to look for unexpected Duplicati processes. From there or Start menu, Resource Monitor as Administrator CPU tab:
If the duplicati server is stopped and i reboot, there cannot be any processes that lock the files.
Technically it should start right up again at boot.
It would be best to check that – and my other advice.
I think we’re talking about two separate issues.
I have no problems with the Duplicati server starting up automatically.
My orginal question was why legacy db’s seemed to be locked when they were no llonger referenced in any backup cfg job.|
Either way, I was finally able to del them.
I have to say actions taken were confusing. It sounded like recreate was for configured DBs:
GUI delete and recreate would leave them at the same paths, so where were failed deletes?
Another odd thing is that Duplicati-server.sqlite is often held open, but idle job DB usually isn’t.
Regardless, looking around at the time might have found something, but problem is now gone.
This outcome is good but leaves a mystery.