
To me, you got the support or fast-fix-type reply from the dev.
The dev seems very busy and behind, and tries fast support.
Of course, the long-term response might be to protect config.
You even gave suggestions, but those don’t happen instantly.
I will suggest some things that might be possible on your own.
This is sadly not in the docs, and not quite what you asked for, but there is
Duplicati.CommandLine.ServerUtil help export
Description:
Export a backup configuration
Usage:
Duplicati.CommandLine.ServerUtil export <backups>... [options]
Arguments:
<backups> The backup id or name to export, use 'all' to export all backups
The problem with export is it goes to a local file. Not safe yet.
If you say back it up (even by BackendTool), you could script.
If you say it should be automatic and only on change, that’s a
GitHub Feature request (or forum, but they get lost) and wait.
If this is “avoid direct restore for basics and guess its config”,
putting an export of the job in its own backup might help that,
but you’re kind of dead if you don’t have info to direct restore.
If you say there should be a Duplicati web login like integrated
paid backup plus storage services use, we’ll see what arrives.
Duplicati started standalone and DIY, and it’s slowly changing.
I’m not the one deciding direction, and speed is always limited.
Meanwhile…
Thanks to @Sarah03 for suggesting a Windows service aid.
The new default is safer, but I forget if old installs are helped.
Is the folder there? Is anything else in there? These are clues.
Depending on upgrade history, there may even be old configs.
Because you cited a location, I thought you didn’t use service.
This is confusing too. TrayIcon might suggest it’s not a service.
What doesn’t fit is “at startup” suggests it’s a Windows service.
The usual TrayIcon launch is at login, even if it talks to service.
What is this really? Windows service requires a manual setup.
Combining Server and TrayIcon is possible, but is more work.
I think Windows changed it. This was once a last-hope restore.
Link? I didn’t spot that issue, going about a week back before this topic.
There has been a debate about backing up job database, as they’re big.
Job database may be getting more user-locked due to more encryption.
That might favor the more portable route of backing up some job export,
so now is a good time to tie this in, but “decided to ditch Duplicati” came.
That can dampen the conversation, but I’m putting effort into another try.
EDIT 1:
Although your AppData folder content might give clues, events might too.
While it would be best to protect against loss, understanding it also helps.
Is this asking if it was an auto-update (unlikely), or did you do it manually?
What version is this currently? Often upgrade leaves old database backup.
It’s just a local backup in the database folder (which I’m asking for info on).