Well, I experimented logging out while doing a restore (again, this is on Linux running KDE). Even if I invoked duplicati with nohup or used disown after invoking it, logging out brings the server to a screeching halt.
It’s hard to be certain, but it looks like it might be leaving incompletely restored files behind.
Also, duplicati does not resume the restore when next invoked.
I guess that running as a service is my only solution (or being careful not to log out when duplicati is active!).
I don’t want to run duplicati as a root service - too much power to wreck havoc, plus I’d prefer it if each user took care of their own configuration of what they backed up and what they didn’t. Hence I’ll need a separate daemon for each user.
(Should I be starting a new topic for the following?)
This raises my next question: I’ll be invoking duplicati-server for each user, so there will be multiple instances listening on different ports. How does a user know what port to connect to in order to manage their duplicati instance? Is there a way to invoke the tray icon connected to the proper server for the current user?
Or is there a way to invoke duplicati (tray icon version) such that the server component daemonizes itself, thereby making itself immune to being killed?
Also, is there a sample service file for invoking duplicati as a daemon?