• Elabajaba@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      11 months ago

      Someone on github has a decent comparison of a bunch of different backup solutions. Afaik Kopia generally uses more memory but is the faster, and restic is pretty fast and doesn’t use as much RAM as kopia (for awhile people recommended against restic as it lacked compression, but they added it in 0.14 last year).

      https://github.com/deajan/backup-bench#in-depth-comparison-of-backup-solutions

      I personally prefer kopia (has a gui to help configure it), but restic is also good. I’m not a fan of Borg because you can’t backup directly to object storage (eg. Backblaze B2/Amazon S3/Wasabi/etc), you have to backup to a local or mounted drive, then upload the backup.

      I’m also waiting on https://github.com/rustic-rs/rustic to get better windows support, as it should use less memory than restic while being as fast, or maybe even faster.

      • calm.like.a.bomb@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        4
        ·
        11 months ago

        I’m not a fan of Borg because you can’t backup directly to object storage (eg. Backblaze B2/Amazon S3/Wasabi/etc), you have to backup to a local or mounted drive, then upload the backup.

        Which in fact is a good thing, because it’s better to have a local copy and an offsite one. rclone copies it for you without issues.

    • Xephopiqua
      link
      fedilink
      arrow-up
      2
      ·
      11 months ago

      I had good experience with BorgBackup and restic. However, I’ve settled with restic since it had the right back ends for me that Borg did not have and I rather like it’s just one static binary instead of Python+C.

      As far as I can see, BorgBackup has a bus factor of one while restic has two to three active contributers.

      Other than that, they are quite comparable, I think.