Live data from Hacker News

Time Machine-style backups with rsync (2018)

samuelhewitt.com

51–57 of 57 posts

Re: Time Machine-style backups with rsync (2018)

#52
post #4

If we spoke about a Linux box, one that prudently ran ZFS, or XFS on top of LVM, it would be possible to make a snapshot before the diffing and sending, so that the snapshot would be indeed point-in-time. IDK if whatever macOS uses for the filesystem supports snapshots. Otherwise, I think, restic or kopia are better for proper backups, and Syncthing for keeping a mirror copy. But the simplicity of this script in char…

> But the simplicity of this script in charming. An important feature of backups is the ability to restore them. As much as I love restic, I have at least one backup target with hard links.

Have you ever faced a case when restic would not restore a backup? Or would not mount a remote backup?

I have a mirror that Syncthing maintains, with some staggered versioning; it seems similar, and should help me immediately in a case of clobbering something. Restic backups helped me several times in cases of catastrophic failures, and are now the default way of moving my stuff to a new machine.

Re: Time Machine-style backups with rsync (2018)

#53
I remember doing my own backups with rsync a super long time ago! It worked pretty well, but it didn't have compression, encryption, desktop integration, or deduplication, and adding anything would be one more script to maintain.

Now I use Kopia, no real complaints there. I used to use Borg but until recently it needed some fussy extra community package to work on Synology.

Re: Time Machine-style backups with rsync (2018)

#54
post #41

Earlier quoted context omitted.

Why? I’m currently trying to decide between Borg and Restic myself. Borg has worked very well for me in the past, and I’m a bit excited by the new Vorta GUI frontend. But I already have a BackBlaze B2 setup for backing up my Mac, and Restic would let me continue to use that as a backup store. I’m interested in hearing about differentiating points between them.

Primarily it's the reason you already know: restic and borg are the same model, but restic doesn't need it to be an ssh-accessible filesystem on the remote end. Restic can send backups almost anywhere, including object storage like your Backblaze B2 (that's what I use with restic, too). I agree with OP: restic is strictly better. There's no reason to use borg today; restic is a superset of its functionality.

Thanks! Then I’ll look more at Restic :)

Re: Time Machine-style backups with rsync (2018)

#55
post #47

Earlier quoted context omitted.

Primarily it's the reason you already know: restic and borg are the same model, but restic doesn't need it to be an ssh-accessible filesystem on the remote end. Restic can send backups almost anywhere, including object storage like your Backblaze B2 (that's what I use with restic, too). I agree with OP: restic is strictly better. There's no reason to use borg today; restic is a superset of its functionality.

Does restic work well with truenas?

I don't know specifically, but it's a self-contained single file Go executable. It doesn't need much from a Linux system beyond its kernel. Chances are good that it'll work.
Post reply on HN