10 mo. ago • 100%

Question regarding Kopia UI vs restic, etc.

I have a small client on the side that I am looking to get more durable off-site backups done. I personally use restic and resticprofile in my homelab without issue. The issue is that I would like to give them some kind of GUI and from what I see, none of the restic ones will do it.

Kopia appears to be roughly the same kind of design so I'm wondering about the KopiaUI. I would be running the backups themselves off the file server itself but would like a GUI to be available via either a desktop OR at least exposed on a port on the file server to hit via a web browser.

Would running KopiaUI in 'server mode' be what I'm looking for? It seems to be but I would like to confirm before researching it any further. Backups would simply be going to backblaze.

4 comments

Backrest is a web GUI for restic

2
It may be possible to create a UI using a monitoring program like Zabbix.

You could create a custom dashboard that displays all the stats that they need to see.

This of course would be for viewing only, not controlling the schedules, retention etc

1
You connect to a repo and start the server mode using CLI, then you open a browser for UI. I use kopia like that

1
- That might be the ticket. I might just try to expose the ui off the box itself and configure a systemd unit or something to run it on boot.
  
  Will probably set up a throwaway VM tomorrow to test it out. Thank you.
  
  Edit: So I didn't quite understand the entire process (and to some degree with the ACL, still don't yet) but this is what I know now.
  
  The two binaries are kopia and kopia-ui. The latter is to be used on a desktop (or something with a window manager) for easy config of the snapshots, etc. The normal kopia binary is CLI only and suitable for servers.
  
  But with the kopia binary (and the ui one presumably) you can start a server with it and then access that from any machine, firewalling dependent of course.
  
  I started that with kopia server start --address 0.0.0.0:51515 --server-username= --server-password= --tls-cert-file /root/my.cert --tls-key-file /root/my.key after having generated a cert and key. You can also just pass --insecure if you don't care about https (ie. testing.)
  
  From there it lists the configured snapshots, etc. This might be exactly what I need and a systemd unit file would be easy enough to create to have this started on boot.
  
  1