Should I use Restic, Borg, or Kopia for container backups?
Should I use Restic, Borg, or Kopia for container backups?
I'm planning to set up proper backups for my server, but I'm not sure which software to use. I've looked for solutions with encryption, compressed, incremental backups. These seem to be the best options:
Does anyone have experience with these, and if so, what was your experience?
EDIT 2023-12-28:
It seems most people are using Restic of which about half mention using a wrapper such as resticprofiles, creatic and autorestic.
| Borg | Restic | Kopia |
|---|---|---|
| 3 | 7 | 5 |
You're viewing a single thread.
IMHO, Duplicacy is better than all of them at all those things - multi-machine, cross-platform, zstd compression, encryption, incrementals, de-duplication.
Note that while they're disingenuously proclaiming themselves to be a "free" tool, the license is actually an unfree proprietary custom license.
Thank you for saving me the trouble of investigating this as an option.
No reason to tolerate proprietary licenses when there are so many viable FLOSS solutions out there.
The licence is pretty clear - the CLI version is entirely free for personal use (commercial use requires a licence, and the GUI is optional). If you don't like the licence, that's fine, but it's hardly 'disingenuous' when it is free for personal use, and has been for many years.
The subscription model is a wee bit off putting. I employ old hardware and don’t wish to be frog marched into an update/grade that could break that.
Have seen it happen before, been in IT too fucking long not to.
Yes, I also work in IT.
The paid GUI version is extremely cautious on the auto-updates (it's basically a wrapper for the CLI) - perhaps a bit too cautious. The free CLI version is also very cautious about making sure your backup storage doesn't break.
For example, they recently added zstd encryption, yet existing storages stay on lz4 unless you force it - and even then, the two compression methods can exist in the same backup destination. It's extremely robust in that regard (to the point that if you started forcing zstd compression, or created a new zstd backup destination, you can use the newest CLI to copy data to the older lz4 method and revert - just as an example). And of course you can compile it yourself years from now.
Thanks for the info, may look into it further.
I mean the tools mentioned also support these features, how does duplicacy and its prorpietary software make them better?