kopia VS vorta

I think Kopia would be great for your use case

https://kopia.io/

It has a great system to snapshot files but only store data if it's changed. I use it in an environment where I can't use something like zfs to snapshot data because I don't have the ability to make decisions about what filesystem we're using. It's been amazing, love it so much!

Thanks for the tip on Kopia. Setting it up now, looks perfect.

https://github.com/kopia/kopia

Kopia - GitHub

I've been happy with: https://kopia.io/

Fairly easy to configure, does snapshots to S3 and has a icon in my tray I can watch :)

I noticed this project while comparing restic/borg and am thinking about trying it.

Initially I thought this was a corporate project and was looking for the monetization model, but then I found https://github.com/kopia/kopia/blob/master/GOVERNANCE.md

I feel like the project might benefit from making their governance model more prominent on the website.

Kopia also means a copy in Polish and the author is Polish. The first paragraph in the software's Github page also confirms the Polish origin of the name: https://github.com/kopia/kopia/

Tangentially, as far as OSS names of Polish go, kopia is pretty tame. A popular UI deduplicating app is called czkawka (hiccup). Now that choice is just mean towards non-Polish speakers. :)

Kopia is great, though it's worth noting for folks on Linux: non-UTF-8 paths aren't stored correctly [1] and xattrs aren't stored [2]. While most folks probably won't care about the former, the latter can could cause issues (eg. losing SELinux labels makes it difficult to restore a backup of the root filesystem on distros that use SELinux).

[1] https://github.com/kopia/kopia/issues/1764

[2] https://github.com/kopia/kopia/issues/544

I used their trial for a bit to test it out with Vorta [1] in a container. Vorta (and Borg) seemed to work fine, until I wanted to restore an archive and I noticed that my recent snapshots were completely empty. Probably because of a misconfiguration on my end though. But it made me look elsewhere. For me backups should be a fire, test and forget solution.

Recently I made the switch to Kopia [2] which seems to have feature parity with Borg (and Restic [3]). It also has a web UI which is way easier to work with than Vorta. And I can easily view, extract and restore individual files or folders from there. This gave me way more confidence about this solution. The only thing I really miss is that I cannot chose different targets for different paths. For instance, with Borg I was able to backup a partial of my Docker appdata to an external source. And I haven't found a way to do this with Kopia. Besides that I'm pretty happy with this solution and I would recommend it.

1. https://vorta.borgbase.com/

2. https://kopia.io/

3. https://restic.net/

There's a few. Off the top of my head

https://github.com/kopia/kopia

Actually yes! It could even be paid in the context of this year's Google Summer of Code:

https://github.com/borgbase/vorta

Or if you join as mentor, you will be supporting the Python Foundation.

If interested, just email the address in my HN profile.

If you need to encrypt your backups (or even if you don't) I would suggest borgbackup and vorta, it makes differential backups so each one after the first is only the size of the changes mine are roughly 50 MiB each, so its much faster and space efficient than whole backups using something like tar or rsync.

Since I know that borg backup it is a pretty solid tool I wanted to give it a try and I ended up choosing Vorta to have a nice GUI experience.

Different UI and backend, but would vorta (borg front end) work?

A bit like me. Got started setting up a webshop for my first startup and had to learn Apache and PHP.

If anyone with similar skills (Python, Docker, Shell) reads this and looks do get started, do check out our Google Summer of Code projects for this year. You'll get paid and can pick any task in this field: https://github.com/borgbase/vorta/wiki/Google-Summer-of-Code...

I had to compile gcalcli, which eventually got merged in the repos. I also compiled Vorta and Grace.

For the client side, you can use either Vortafor graphical clients, or borgmatic for headless servers. (Or just borg, but borgmatic is better imo)

Over at Vorta (feature branch) we mostly adjusted to the latest betas. So I expect to have support for both versions, once there is an RC. Borgmatic added support in Oct.

We already maintain a UI for Borg, if you're looking for that. It's open source and included in many distros, like Debian and Fedora. Check it out here: https://github.com/borgbase/vorta