

Sorry, I must’ve misremembered about systemd. It’s how my installs start up, and the unit file is not in the usual location for systemd units I’ve created myself, so my assumption was it came with Kopia. There is no systemd timer though, and one isn’t needed.
Edit: Just confirmed no systemd file came with kopia on my system either, my mistake.
in the past week, it did not backup anything. Hence, there is no scheduler built into kopia automagically as described/ hinted in the docs.
Was Kopia running during that time?
If you run a Kopia command, then it will perform the instructed task, and then exit. It will obviously not do anything after completing whatever command was given, as the process will have exited, leaving no kopia process running on the system. This is for when you use it in cron or your own scripts.
The other way of doing things is to run it in server mode kopia server start, which will set it running as a background daemon. When running, it allows you to log into the web interface or configure it via cli to do whatever you like. And as long as the process starts along with the host system, that’s all there is to it.
How the daemon is set up to start, doesn’t really matter.







“Hey… Nice mass surveillance system you got there, mind if I have a turn?”
It boggles my mind how some people thought privact was worthless, and harmless to give up.