Live data from Hacker News

Restic: Backups done right

restic.net

31–40 of 108 posts

Re: Restic: Backups done right

#31
Restic is great! It has worked flawlessly for me for several years.

Anyone knows if there is plan to add Reed Solomon erasure coding, just in case there will be errors in repository? Something like Par2.

Asymmetric encryption could also be useful in some situations. Perhaps they could just use Age for the asymmetric encryption backend (unfortunately Age offers only 128 bits of security in its symmetric encryption, so it’s not recommended for long term storage, because of the save-now decrypt-later attack). But I expect a stable quantum resistant plug-in appearing next year or so.

Re: Restic: Backups done right

#32
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.

Re: Restic: Backups done right

#33
post #31

Restic is great! It has worked flawlessly for me for several years. Anyone knows if there is plan to add Reed Solomon erasure coding, just in case there will be errors in repository? Something like Par2. Asymmetric encryption could also be useful in some situations. Perhaps they could just use Age for the asymmetric encryption backend (unfortunately Age offers only 128 bits of security in its symmetric encryption, so…

Afaik not yet, there was some discussion here: https://github.com/restic/restic/issues/804

Re: Restic: Backups done right

#34
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/…

Keeping with the name scheme, there is also duplicacy - https://github.com/gilbertchen/duplicacy

Re: Restic: Backups done right

#35
post #26

Big fan of restic! The only feature I found missing was the ability to browse historical snapshots like regular files. I wrote and now use the rsync-based, browsable, incremental backup CLI: https://rincr.com/

What do you mean by that? "restic mount" has been part of restic since the very start.

That command works well and accomplishes some of what rincr what built to solve. For example, when I mention browse-ability, I mean on the backup host without any dependencies so I can use standard file tools and browsers.

I also needed both "pull" (backup remote files) and "push" (backup local files) backup features and if I'm not mistaken restic still only supports the "push" model.

EDIT: Added more details

Re: Restic: Backups done right

#36
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.

Nice. Using `.gitignore` would simplify my Restic, Borg/Borgmatic, and Rsync-based backup scripts/configs. (Right now, I end up duplicating the same information in a few places, not very well.)

Re: Restic: Backups done right

#37
post #23
post #21

What's the best way to backup a managed Postgres from DO to another cloud?

Not sure what DO managed PostgreSQL supports, but PostgreSQL streaming replication would seem like the natural way to go.

They don't support that, forgot to clarify that in my comment. Thanks!

Re: Restic: Backups done right

#38
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 have tested all of these also, and settled on borg + borgmatic. It has been absolutely rock solid. Borgmatic just rounds everything together in such a nice way. The documentation is great.

I'm pushing it all to a Hetzner storage box, as well as a local NAS. Super affordable!

Re: Restic: Backups done right

#39
post #6
post #4

https://github.com/garethgeorge/backrest going nicely with restic i do miss functionality of configurable full/incremental backups like in duplicity

What do you miss about it? In restic, every snapshot has the speed and size of an incremental backup, but the functionality of a full backup.

sometimes you just must have a new full backup every N days/weeks. it a more "smooth" way to deal with potential corruption in repo that might be undetected (without dealing with all suggested workarounds) and in some cases compliance/certification requires it

Re: Restic: Backups done right

#40
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/…

BorgBackup is also my choice. More features, but that's not necessarily a good (or bad) thing if Restic does everything you need.
Post reply on HN