Most active commenters

    ←back to thread

    Restic: Backups done right

    (restic.net)
    231 points fanf2 | 15 comments | 13 Oct 24 17:42 UTC | HN request time: 0.627s | source | bottom
    1. alibert ◴[13 Oct 24 18:35 UTC] No.41830358[source]▶
    Been using Restic for a while but I was wondering how does it compare to:

    - Rustic https://rustic.cli.rs

    - Kopia https://kopia.io

    replies(7): >>41830408 #>>41830448 #>>41830483 #>>41830842 #>>41830884 #>>41830896 #>>41847748 #
    2. asteroidburger ◴[13 Oct 24 18:40 UTC] No.41830408[source]▶
    Rustic is a rewrite of Restic from Go to Rust. See https://rustic.cli.rs/docs/comparison-restic.html
    replies(1): >>41833800 #
    3. aliasxneo ◴[13 Oct 24 18:44 UTC] No.41830448[source]▶
    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.

    replies(2): >>41830584 #>>41830615 #
    4. BoingBoomTschak ◴[13 Oct 24 18:47 UTC] No.41830483[source]▶
    I vaguely remember Kopia having partly mitigated Restic's issues with memory usage.
    5. dicytea ◴[13 Oct 24 18:59 UTC] No.41830584[source]▶
    You dropped the l: https://rustic.cli.rs/docs/comparison-restic.html
    6. tredre3 ◴[13 Oct 24 19:03 UTC] No.41830615[source]▶
    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.

    replies(1): >>41832671 #
    7. riedel ◴[13 Oct 24 19:33 UTC] No.41830842[source]▶
    https://www.patpro.net/blog/index.php/2024/03/07/3590-borg-k...
    8. Scandiravian ◴[13 Oct 24 19:38 UTC] No.41830884[source]▶
    I switched to rustic a couple of months ago due to it being able to filter based on .gitignore files. Have done a few test restores and everything has worked well so far
    9. snorremd ◴[13 Oct 24 19:40 UTC] No.41830896[source]▶
    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.
    replies(3): >>41830991 #>>41833598 #>>41840498 #
    10. neilv ◴[13 Oct 24 19:52 UTC] No.41830991[source]▶
    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.)
    11. tacticus ◴[13 Oct 24 23:28 UTC] No.41832671{3}[source]▶
    "rewrite-it-in-rust-wrapping-c"
    12. githubalphapapa ◴[14 Oct 24 02:15 UTC] No.41833598[source]▶
    At first I thought that sounded great, but then I realized that that would exclude files that I want to be backed up, like `dir-locals-2.el`, which should be excluded from git, but should also be backed up. There doesn't seem to be a great solution to that in general.
    13. rjrdi38dbbdb ◴[14 Oct 24 02:53 UTC] No.41833800[source]▶
    It looks nice, but until they support FUSE mounting, I'll stick with restic.
    14. Too ◴[14 Oct 24 18:39 UTC] No.41840498[source]▶
    Wouldn’t you back up your git repos by pushing them somewhere? Even if that somewhere is a different directory on the same drive. Backing up your local working copy sounds a bit odd.
    15. tinodb ◴[15 Oct 24 12:15 UTC] No.41847748[source]▶
    From the rustic readme:

    > rustic currently is in beta state and misses regression tests. It is not recommended to use it for production backups, yet.