Discussion of my approach to using restic + rclone + Backblaze B2 here:
Restic: Backups done right
61–70 of 108 posts
Re: Restic: Backups done right
#62Restic is awesome for moderate operational scale, but when it's got to backup thousands of storage block devices with arbitrary number of files on them, it just doesn't really work.
Is there anything cool people use for Ceph-RBD backups nowadays?
For now, the only thing in the OSS world that doesn't choke at this scale is Benji, but it looks like it's not really maintained anymore, and I worry it may not support newer Ceph versions.
Re: Restic: Backups done right
#63Earlier quoted context omitted.
I perused the Rustic website and they have a direct comparison of Restic here: https://rustic.cli.rs/docs/comparison-restic.htm . At face value I thought it was just, "because it's Rust," but it does appear to have a few additional features. I haven't used either, though.
Rustic was started by a former restic contributor. My impression at the time was that he was frustrated with poor collaboration from restic maintainers (slow/no response to his PRs). So it's a bit more than just "rewrite-it-in-rust". Many of his rejected/ignored restic PRs ended up being features in rustic: cold storage support, config file support, resumable operations, webdav server, etc.
"rewrite-it-in-rust-wrapping-c"
Re: Restic: Backups done right
#64Other 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'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 latest version does require python 3.9.0, but that's already 4 years old.
Re: Restic: Backups done right
#65Big 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/
Only feature missing for me was passwordless backups
Re: Restic: Backups done right
#66Earlier quoted context omitted.
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?
I've been using it for years with zero problems.
Re: Restic: Backups done right
#67Faster alternatives I recommend:
* Kopia: many features, also great for desktop GUI users
* bupstash: The fastest, lowest RAM. I use it to backup 1B files daily (200TB). Ransomware-proof asymmetric multi key crypto. Less features.
Re: Restic: Backups done right
#68Other 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.
I used Duplicity (via the Gnome Déjà Dup GUI) for years, but Borg turned out to be a lot faster at making the backups, at least for my laptop home dir backups. Like an order of magnitude faster. I don't think I ever tried to hand-configure Duplicity, though.
Re: Restic: Backups done right
#69Duplicity is my go because it integrates so well with pgp signing/encryption. Other popular alternatives like borg and restic just do not have it.
Re: Restic: Backups done right
#70Duplicity is my go because it integrates so well with pgp signing/encryption. Other popular alternatives like borg and restic just do not have it.
I do wish there were a way to allow a machine to perform backups without also allowing to read them. I generate per-machine secret keys for restic, then encrypt those keys to a set of GPG recipients, and store them alongside the backup data. I did have to roll my own solution for this using s3cmd etc but its not too bad.