Comment

Comment on [Help] Improving HDD storage setup for personal server

It’s a fedora server.

according to kopia’s repo, there is no official systemd service github.com/kopia/kopia/issues/2685 and there is none on my system.

in the past week, it did not backup anything. Hence, there is no scheduler built into kopia automagically as described/ hinted in the docs.

I just wrote a systemd service and timer and I’ll see if it works. I’m not the best in using systemd. I dislike it, I like cron for it’s simplicity.

Even if it works then, I wouldn’t recommend it to anyone because info about the scheduler is rare and the docs do not even cover the topic.

source

Sort:hotnew top

MentalEdge@sopuli.xyz ⁨4⁩ ⁨days⁩ ago
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 is it came with Kopia. There is no systemd timer though, and one isn’t needed.

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 Kopia commands, 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.

Starting it up in in server mode kopia server start however, which is what you do to have 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. And if you want to use your own scheduling, (cron or a systemd timer) you can do that, too.

source
- selfmate@lemmy.zip ⁨4⁩ ⁨days⁩ ago
  all good. thanks for exchanging our experience :)
  
  kopia wasn’t running durin the week. I didn’t look into the server configuration since it introduces user handling and that seemed to be overkill for the task but running as daemon would lead to a funcitoning system of course.
  
  this is my kopia.service file in case some else finds it and is interested in it
  
  [Unit] Description=kopia backup
  
  [Service] User=root ExecStart=$HOME/bin/backup_kopia
  
  [Install] WantedBy=multi-user.target
  
  where $HOME/bin/backup_kopia contains
  
  #!/bin/bash /usr/bin/kopia repository connect filesystem --path $KOPIA_REPO --password $KOPIA_PASSWORD /usr/bin/kopia snapshot create $HOME/folder_to_backup
  
  and my kopia.timer
  
  [Unit] Description=Run kopia backup
  
  [Timer] OnCalendar=hourly Persistent=true
  
  [Install] WantedBy=timers.target
  
  source