Yes we are, and I’m reluctant to keep explaining it, so please review the previous explanations which explain how AUR makes systemd service come up as a powerless user, with databases located where it wants, and not where your databases actually had been. The latter raises the question of whether you were ever actually on systemd service, or got in TrayIcon another way.
UserName is easily explainable. Manual launch as you is you. Systemd launch is duplicati, as AUR unit file makes it so. Usually people just edit the unit file to not do that, so run as root and have good access but more security risk. I’m not sure if they insist on having Tray Icon as well, because that takes special care to launch with --no-hosted-server to get to systemd server.
Alternatively you just let AUR do its thing on systemd and you do yours as you just by TrayIcon launch. Launch at login should be available in Arch or EOS docs, or EOS forum can likely help.
One subtle point on your manual launch is that the jump from BaseVersion to ServerVersion is from an autoupdate that you installed that’s still hanging around. You can just find and delete it.
Downgrading / reverting to a lower version
gives some possible locations where you can look, maybe you remember user that updated, or you can just search in root shell with something like find / -mount -name '*2.0.7.101*' which will help find the subfolder called updates where Duplicati puts its installed autoupdates.
Downgrade sometimes hits database version snags, but this one just needs an update deletion.