Been using Restic for a while but I was wondering how does it compare to: - Rustic https://rustic.cli.rs - Kopia https://kopia.io
I vaguely remember Kopia having partly mitigated Restic's issues with memory usage.
Restic: Backups done right
11–20 of 108 posts
Re: Restic: Backups done right
#12I’m more fan of BorgBackup, but you have to couple it with I.e. rclone for it to make backups to cloud object storage. But that opinion is based on my particular use case, probably would be using restic if direct to cloud was a better choice.
Re: Restic: Backups done right
#13Other 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.
Re: Restic: Backups done right
#14I’m more fan of BorgBackup, but you have to couple it with I.e. rclone for it to make backups to cloud object storage. But that opinion is based on my particular use case, probably would be using restic if direct to cloud was a better choice.
Borg 2.0 supposedly will support cloud backups out of the box.
Re: Restic: Backups done right
#15Been using Restic for a while but I was wondering how does it compare to: - Rustic https://rustic.cli.rs - Kopia https://kopia.io
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.
You dropped the l: https://rustic.cli.rs/docs/comparison-restic.html
Re: Restic: Backups done right
#16I'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 fans run. Despite that it still seems to be the best free software option around
Re: Restic: Backups done right
#17Been using Restic for a while but I was wondering how does it compare to: - Rustic https://rustic.cli.rs - Kopia https://kopia.io
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.
Re: Restic: Backups done right
#18Other 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.
Re: Restic: Backups done right
#19I've tried many options and ended up distching Restic for Borg and then Borg for Kopia, which was IMO the best option.
Re: Restic: Backups done right
#20There is also autorestic - A simplified YAML-based configuration for dealing with Restic backups: https://github.com/cupcakearmy/autorestic