I have a backup that I ported over from a Linux host to a Windows host (exported JSON configuration, reimported into Windows, then edited dlist files to match new source paths).
I found that if I try to run the database repair or the backup through the web UI, it starts but after a little bit of network activity contacting my backend (OneDrive), the activity stops and the progress bar still shows 0 progress (e.g. Verifying backend data). At that point, there is zero disk activity, no CPU use, and no network activity from the Duplicati processes (running as a service).
In an attempt to see if there was more feedback about what might be going wrong I decided to run those actions directly through the Duplicati.CommandLine.exe program, and to my surprise, everything worked.
When rebuilding the database, it contacted the backend and downloaded a bunch of files, finally rebuilding a new SQLite database.
When running the backup, it contacted the backend and then started a whole lot of disk and CPU activity, examining all the files on my source, before finally uploading changes successfully.
The backup command I ran was obtained using the Export feature from the web interface and choosing the Command line option. I ran it as the local system account, which is what my service is running as (default settings).
Are actions initiated from the web UI very different than those being run by the command line program? How can I fix my front-end so that I can control the back-ups from there instead of having to use the command line tool?