This is why I’m asking @marcosvrs what IDx means. I suspect they’re job database backups with random ID characters. I forget what a Duplicati-server.sqlite backup is called, but it shouldn’t happen because there was no version upgrade to cause backup (whereas there was for the job databases).
So we know no file names, and no precise file times. ls -l --full-time can show precise times.
Size of backup ID3 is less than non-backup ID3, and its date is older. Might be OK, but May 2 date is
before 2.0.6.1, so what was it on? The system looks to be in in ahead-of-UTC timezone, as it shows
May 4 dates on a (to me) May 3 post. Or maybe the clock is just set wrong. What time zone is it in?
Simple grep for one of the ID# strings in it would help. Heavy approach is install and run sqlitebrowser.
Web interface empty task list when not on local machine is a weird waiting-for-originator problem that sounds like server systeminfo data didn’t arrive, so it looks like jobs aren’t there on some browsers.
There are other screens broken as well, so it should be possible for @marcosvrs to try that testing.