Creating a new backup job touches on this a bit in one use case, but same is true for any new backup job:
When importing a backup job from a configuration file, a new database will be created, using a random filename.
Database management “Local database path” shows generated name, but file isn’t created until a backup. Although I’m not really familiar with this DB code, I think this is the same case of assigned-but-not-created. Server mapping to DB is in Duplicati-server.sqlite. I knew of dbconfig.json but wasn’t sure of how it’s used. Looking further just now, I think this can maintain mappings for CLI use but (as said) server is independent.
This is the expectation of integrated tools, but they’re independent. Rationale is quoted above. Downside is expectations and frustration of those who don’t know the scheme. Once scheme is set, change is difficult:
I would certainly make a new tool (not add server-control to the current CLI). IMO it would be even more confusing if there is a CLI tool that can work with- and without the server, as it will work differently in the two cases (not write logs, not find database etc).
This messaging might be fixable (I’m not sure how much rearranging it would need). Just stop, then insist Feel free to file an issue asking for more friendly handling of the missing-because-it-was-just-invented DB.