There is also autorestic - A simplified YAML-based configuration for dealing with Restic backups: https://github.com/cupcakearmy/autorestic
I hadn’t seen autorestic before so I can’t compare them, but there’s resticprofile
Restic: Backups done right
51–60 of 108 posts
Re: Restic: Backups done right
#52Try 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 would be a nice thing.
Restic is very very good. My only nervousness is the backup format is so opaque, you need a working copy of Restic to restore from it. The format is documented though and of course the code is open source, so I think it's probably fine in practice.
Re: Restic: Backups done right
#53https://github.com/garethgeorge/backrest going nicely with restic i do miss functionality of configurable full/incremental backups like in duplicity
Backrest is great. It makes it very easy to configure restic backups and do the restores.
Re: Restic: Backups done right
#54Pruning takes forever in Restic, which is why we migrated away from it.
Re: Restic: Backups done right
#55Other 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/…
Duplicity is solid, I’ve been using it since over a decade, and it’s a standard package on Debian-based distributions. Never had any hiccups (and I run regular backup validations).
These threads about backup tools come up regularly, and I always wonder if I’m missing something important about the other tools.
Re: Restic: Backups done right
#56Earlier 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
> I mean on the backup host without any dependencies so I can use standard file tools and browsers.
This means the backups are not encrypted though, and is something you really have to think twice before requiring
> "pull" (backup remote files)
You can mount the server to backup on the backup host, or you can ssh from the backup host to the server to backup, call `tar cf - /folder`, and ingest that from stdin on the backup host. Both will retransmit the totality of the files to backup
Re: Restic: Backups done right
#57Other 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…
I write Python day to day, but even I use Restic for the single binary. I take a lot of comfort in being able to keep the backup executable adjacent to the backup blobs. While I believe Borg now has a distributable binary, Go has it in its blood to make easy deployment without tricks.
Re: Restic: Backups done right
#58Pruning takes forever in Restic, which is why we migrated away from it.
What did you migrate to?
Re: Restic: Backups done right
#59Which 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.)
Re: Restic: Backups done right
#60I've been using Restic for servers, but ended up going with Kopia for machines that are not always on, like laptops. It has the advantage that it will take something of an opportunistic approach where it will start backing up if it hasn't done so in a while, and seems to be able to restart with aplomb if it gets interrupted (machine shutdown or laptop lid closed).
That and being able to have multiple machines writing to a shared repository at the same time is handy. I have the kids' Windows computers both backing up to the same repo to save a bit of storage. (Now if only Kopia supported VSS on Windows without mucking around with dubious scripts.)