Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Restic: Backups done right

restic.net

Post reply on HN
Print view View original

91–100 of 108 posts

Re: Restic: Backups done right

#91

Post by crossroadsguy »

confusedalex wrote: post #83
NelsonMinar wrote: post #52

Try BackRest if you want a nice frontend to Restic. You can configure Restic from the command line but it's pretty awkward. BackRest has a nice simple web GUI and makes basic automation very easy. https://github.com/garethgeorge/backrest I'm surprised no one is selling Restic hosting as a straight up service. BackBlaze works well with Restic but the configuration is a little manual and clumsy. A packaged solution wou…

Despite the name Borgbase [0] offers Restic hosting, with actual documentation on how to set it up. Hetzner [1] also offers Restic [0] https://www.borgbase.com/ [1] https://www.hetzner.com/storage/storage-box/

Huh. Interesting. Didn't know borgbase supports restic as well. I already have a plan there for vorta/borg. Thanks.

Re: Restic: Backups done right

#92

Post by wazoox »

lizknope wrote: post #89

In the 90's I remember using various backup tools that had their own custom format. I decided that I wanted my backup to be just wanted files on a normal filesystem without being stored in some kind of special format. I realize that this means compression and block level deduplication is harder but those are tradeoffs that I can accept. I've been using rsnapshot (or it's predecessor script) for 20 years now. It's a w…

Yes rsnapshot is fantastic. Plus with some simple configuration you can make your "rsnapshots" appear as legitimate snapshots from your Samba server to Windows clients.

Re: Restic: Backups done right

#93

Post by crossroadsguy »

riedel wrote: post #18
kayson wrote: post #13

Other popular choices include borg, duplicity, and duplicati. After evaluating these and others mentioned in the comments, I ended up using borg with borgmatic to define homelab backups with yaml files that are version controlled in gitea and deployed using ansible. I also use duplicity to back up my sister in laws storefront website to backblaze. I've been quite happy with both. https://borgbackup.readthedocs.io/en/…

I'd throw in kopia[0], fast, many features and easy to use across platforms. [0] https://kopia.io/

Last time I tried Kopia was more like "select ONE folder to backup and add ONE destination to SNAPSHOT it to". While it is very simplistic and would be lovely in many use cases - for a home/personal backup which often requires granularity of inclusion and exclusion it just didn't make any sense. I am not sure whether that has changed.

Re: Restic: Backups done right

#94

Post by crossroadsguy »

sph wrote: post #42
kayson wrote: post #13

Other popular choices include borg, duplicity, and duplicati. After evaluating these and others mentioned in the comments, I ended up using borg with borgmatic to define homelab backups with yaml files that are version controlled in gitea and deployed using ansible. I also use duplicity to back up my sister in laws storefront website to backblaze. I've been quite happy with both. https://borgbackup.readthedocs.io/en/…

I chose restic because borg was slow, buggy and an unwieldy pile of Python, not the best language for deployment on heterogeneous Linux systems. Restic on the other hand is slow, but never crashed on me and is distributed as a single binary. The only thing I dislike about restic is that it does not have a simple config file where you define your backup settings. Instead I had to write my own backup.sh that I deploy e…

> it does not have a simple config file where you define your backup settings.

Will this https://github.com/garethgeorge/backrest/discussions/188 work for you?

Also, I can add directory file to include exclude directly to this config or to separate files as I please and just refer in this config.

Re: Restic: Backups done right

#95

Post by crossroadsguy »

ajvs wrote: post #80
manuel_w wrote: post #59

Which one is more resistant to bitrot, Restic or Borg Backup? (Yes, bitrot might better be mitigated at the filesystem layer, but I'm not switching to ZFS, btrfs or bcache-fs anytime soon.)

Not sure but I know that Vorta (borg GUI) does automatic consistency checking using `borg check ` regularly.

Vorta offers you "Prune" customisation at the bottom of 'Archives' tab and "check" (validate repo) along with backup settings on 'Schedule' tab.

Re: Restic: Backups done right

#96

Post by k_g_b_ »

kayson wrote: post #64
sph wrote: post #42

Earlier quoted context omitted.

I chose restic because borg was slow, buggy and an unwieldy pile of Python, not the best language for deployment on heterogeneous Linux systems. Restic on the other hand is slow, but never crashed on me and is distributed as a single binary. The only thing I dislike about restic is that it does not have a simple config file where you define your backup settings. Instead I had to write my own backup.sh that I deploy e…

I've never had any crashing or big issues with borg, and it's generally considered to be faster than restic. I'm sure there are more recent benchmarks, but as of Dec 2022, borg wins by a fair bit [1]. For installation, I set up a dedicated virtualenv for borg and borgmatic installation then symlink into /usr/local/bin. This is also automated with ansible and has worked on every distro and version I've used. The lates…

Agreed on no crashing/issues. I always use the provided Borg "single binary" https://borgbackup.readthedocs.io/en/latest/installation.htm... that unpacks everything into /tmp and naturally is larger than the restic binary. That isn't an issue on my systems.

Restic has no unencrypted mode for reasons - you must use an empty password and additional flag instead. If your backups will already be encrypted in other ways you'll still pay encryption overhead.

Re: Restic: Backups done right

#98

Post by synthomat »

o_____________o wrote: post #76
kayson wrote: post #13

Other popular choices include borg, duplicity, and duplicati. After evaluating these and others mentioned in the comments, I ended up using borg with borgmatic to define homelab backups with yaml files that are version controlled in gitea and deployed using ansible. I also use duplicity to back up my sister in laws storefront website to backblaze. I've been quite happy with both. https://borgbackup.readthedocs.io/en/…

& Arq https://www.arqbackup.com/

Arq is awesome! Unfortunately not suitable for headless systems.

Re: Restic: Backups done right

#99

Post by evulhotdog »

dmw_ng wrote: post #16

I'm a restic user, but have resisted the urge to attempt a bikeshed for a long time, mostly due to perf. It's index format seems to be slow and terrible and the chunking algorithm it uses (rabin fingerprints) is very slow compared to more recent alternatives (like FastCDC). Drives me nuts to watch it chugging along backing up or listing snapshots at nowhere close to the IO rate of the system while still making the fa…

You should check out Kopia. It’s absolutely wonderful, is fast, has similar features, and has a GUI if you’re into that.

Re: Restic: Backups done right

#100

Post by Too »

snorremd wrote: post #32
alibert wrote: post #7

Been using Restic for a while but I was wondering how does it compare to: - Rustic https://rustic.cli.rs - Kopia https://kopia.io

A killer feature rustic has over restic is built-in support for .gitignore files. So all your dependencies and build output is automatically ignored in your backups.

Wouldn’t you back up your git repos by pushing them somewhere? Even if that somewhere is a different directory on the same drive. Backing up your local working copy sounds a bit odd.
Post reply on HN