Hacker News new | ask | show | jobs
by aborsy 383 days ago
Restic is the winner. It talks directly to many backends, is a static binary (so you can drop the executable in operating systems which don’t allow package installation like a NAS OS) and has a clean CLI. Kopia is a bit newer and less tested.

All three have a lot of commands to work with repositories. Each one of them is much better than closed source proprietary backup software that I have dealt with, like Synology hyperbackup nonsense.

If you want a better solution, the next level is ZFS.
2 comments
PunchyHamster 383 days ago
Kopia is VERY similar to Restic, main differences is Kopia getting half decent UI vs Restic being a bit more friendly for scripting

> If you want a better solution, the next level is ZFS.

Not a backup. Not a bad choice for storage for backup server tho

link
omnimus 382 days ago
But aren't ZFS snapshot replicas a backup? It seems that systems like TrueNAS went this way and you then don't need other solution.
link
jopsen 382 days ago
IMO the UI is a killer feature.

I don't need to configure and monitor cron jobs.

link
seymon 383 days ago
I am already using zfs on my NAS where I want my backups to be. But I didn't consider it for backups till now
link
aeadio 383 days ago
You can consider something like syncthing to get the important files onto your NAS, and then use ZFS snapshots and replication via syncoid/sanoid to do the actual backing up.
link
aborsy 383 days ago
Or install ZFS also on end devices, and do ZFS replication to NAS, which is what I do. I have ZFS on my laptop, snapshot data every 30 minutes, and replicate them. Those snapshots are very useful, as sometimes I accidentally delete data.

With ZFS, all file system is replicated. The backup will be consistent, which is not the case with file level backup. With latter, you have to also worry about lock files, permissions, etc. The restore will be more natural and quick with ZFS.

link
fc417fc802 383 days ago
I can't speak to zfs but I don't find btrfs snapshots to be a viable replacement for borgbackup. To your filesystem consistency point I snapshot, back the snapshot up with borg, and then delete the snapshot. I never run borg against a writable subvolume.
link