Been looking into resource constraining Kopia through systemd to prevent the Go binary from eating through too many resources. Anyone running a system like this?
Been looking into resource constraining Kopia through systemd to prevent the Go binary from eating through too many resources. Anyone running a system like this?
I have run it for several years overnight without issue, backing up around 10GiB, but can only vouch for the stability of the solution and not its behaviour under constrained resources. I had come from duplicati which always ended up with a corrupt database I could not restore from. This project has been a solid replacement, so I would recommend giving it a go.
Have you tried running from CLI, or only through the server?
I run the schedule through the server, which also allows you to browse the snapshots, restore individual files from them, and validate what has been backed up.