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

41–50 of 108 posts

Re: Restic: Backups done right

#41

Post by homebrewer »

thekashifmalik wrote: post #35
dmd wrote: post #26

Earlier quoted context omitted.

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

If you're doing pull to prevent remotes from destroying old backups (in case of malware takeover, etc), this can be solved by running rest-server with --append-only

https://github.com/restic/rest-server

It 403's any attempt to overwrite or delete old data.

Re: Restic: Backups done right

#42

Post by sph »

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 everywhere on my personal and production machines. Paired with rsync.net for storage and healthchecks.io for notifications.

Re: Restic: Backups done right

#45

Post by notherhack »

Restic 0.17.1 was released last month. The home page says "During initial development (versions prior to 1.0.0), maintainers and developers will do their utmost to keep backwards compatibility and stability, although there might be breaking changes without increasing the major version."

So worth a peek but still under construction.

Re: Restic: Backups done right

#46

Post by notherhack »

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

The Borg site says Windows support is "experimental, no binaries yet". Is that still true?

Re: Restic: Backups done right

#47

Post by luoc »

thekashifmalik wrote: post #35
dmd wrote: post #26

Earlier quoted context omitted.

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

Browsing without dependencies is a bit tricky due to a) deduplication, b) encryption and c) compression of restic's backups.

Re: Restic: Backups done right

#48

Post by mongol »

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/

I have seen Kopia mentioned from time to time but never as often as borg. Does it have a good reputation?

Re: Restic: Backups done right

#49

Post by ray_v »

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…

Honest question, but do you not consider environment variables to be a form of simple config?

https://restic.readthedocs.io/en/stable/040_backup.html#envi...

Re: Restic: Backups done right

#50

Post by abhinavk »

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…

Use resticprofile or autorestic for configuration file or to run scheduled jobs.
Post reply on HN