I am using duplicati and thinking of switching to Borg. What do you use and why?

  • There is no such thing as the objectively best solution. Each tool has advantages and disadvantages. And every user has different preferences and requirements.

    Personally, I am using Borg for years. And I have had to restore data several times, which has worked every time.

    In addition to Borg, you can also look at Borgmatic. This wrapper extends the functionality and makes some things easier.

    And if you want to use a graphical user interface, you can have a look at Vorta or Pika.

  • flux ( flux@beehaw.org ) 
    link
    fedilink
    arrow-up
    8
    ·
    3 years ago

    Kopia has served me great. I back up to my local Ceph S3 storage and then keep a second clone of that on a raid.

    Kopiahas good performance and miltiple hosts can back up tp it concurrently while preserving deduplication – unlike borgbackup.

    • aliens ( aliens@infosec.pub ) 
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 years ago

      Kopia has been working great for me as well. It’s simple, versatile and reliable. I previously used Duplicati but kept running into jobs failing for no reason, backup configurations missing randomly and simple restores taking hours. It was a hot mess and I’m happy I switched.

      • Parsnip8904 ( Parsnip8904@beehaw.org ) 
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 years ago

        I want to love kopia but the command line syntax feels unnatural to me. I don’t know why either. For the whole month I test drove it, I had to look up every single time how to do something. Contrast this with restic which is less featureful in some ways but a few days in it felt like I was just using git.

        • aliens ( aliens@infosec.pub ) 
          link
          fedilink
          English
          arrow-up
          3
          ·
          3 years ago

          I never used the command line with Kopia besides starting it up in server mode and used the web based GUI to configure, it was pretty simple to get everything setup that way. You may want to give it another try using Kopia in that mode.

            • flux ( flux@beehaw.org ) 
              link
              fedilink
              English
              arrow-up
              3
              ·
              3 years ago

              You can use the web ui remotely.

              Personally I use it from command line, though, and my only complaint is that it’s too easy to start a backup you didn’t intend to… Buut if you’re careful about usong the kopia snapshot command then it’s fine.

              • Parsnip8904 ( Parsnip8904@beehaw.org ) 
                link
                fedilink
                English
                arrow-up
                2
                ·
                3 years ago

                Oh I thought the webui was only for server mode.

                I just quickly glanced through the manuals of both restic and kopia. I think my trouble with kopia is that its style feels kind of weird. I’m just not able to wrap my head around it well.

                kopia snapshot create /dir is shorter but more confusing than restic -r repo backup /dir

  • Karce ( karce@wizanons.dev ) 
    link
    fedilink
    arrow-up
    7
    ·
    3 years ago

    I use btrfs snapshots and btrbk

    btrfs is a great filesystem and btrbk complements it easily. Switching between snapshots is also really easy if something goes wrong and you need to restore.

    Archwiki docs for btrfs: https://wiki.archlinux.org/title/Btrfs#Incremental_backup_to_external_drive

    Of course you’d still want a remote location to backup to. You can use an encrypted volume with cloud storage. So google drive, etc all work.

    • flux ( flux@beehaw.org ) 
      link
      fedilink
      arrow-up
      2
      ·
      3 years ago

      You will reconsider calling strategy a backup should the filesystem get corrupted for whatever reason.

      I’ve tested my full system backup restore once with btrfs. Worked out fine.

      • derek ( derek@lemmy.one ) 
        link
        fedilink
        arrow-up
        1
        ·
        3 years ago

        Maybe Photoprism isn’t a backup strategy, but Syncthing for sure is, because you can have multiple backup units in it.

        I’m additionally use software RAID on one of devices, that receives Syncthing backups.

  • I’ve been using restic. It has built-in dedup & encryption and supports both local and remote storage. I’m using it to back up to a local restic-server (pointing to a USB drive) and Backblaze B2.

    Restores for single or small sets of files is easy: restic -r $REPO mount /mnt Then browse through the filesystem view of your snapshots and copy just like any other filesystem.

  • I use NixOS so all my system configuration is already saved in my NixOS configs, which I save on GitHub. For dotfiles that aren’t managed by NixOS I use syncthing to sync them between my devices, but no real backup cause I can just remake them if I need to, and things like my Neovim and VSCode configs are managed by my NixOS configs so they’re backed up as well.

  • TDCN ( TDCN@feddit.dk ) 
    link
    fedilink
    arrow-up
    5
    ·
    3 years ago

    Rsync is great but if you want snapshots and file history rsnapshot works pretty well. It’s based on rsync but for every sync it creates shortcuts for existing files and only copies changes and new files. It saves space and remains transparent for the user. FreeFileSync is also amazing

  • ipkpjersi ( ipkpjersi@lemmy.one ) 
    link
    fedilink
    arrow-up
    5
    ·
    3 years ago

    I use my own scripts with rsync etc, I don’t back up my OS itself since I have installing it automated with scripts as well. I just back up specific things I need with my scripts.

      • ipkpjersi ( ipkpjersi@lemmy.one ) 
        link
        fedilink
        arrow-up
        2
        ·
        3 years ago

        They’re very personalized to my setup, so they’re not particularly useful in a general sense - I’d recommend something more like using this guide which seems to be pretty good: https://jumpcloud.com/blog/how-to-use-rsync-remote-backup-linux-system

        Learning bash has been great for me, it’s helped a ton being able to automate so many different things even just like installing and configuring specific applications to work the way I want, etc

        I think a script to manually run for manual backups plus a different script to run for automatic backups scheduled via cronjob is a great way to go.

        There’s of course more advanced things like zfs snapshots which I won’t get into, but I think my explanation as a general concept should be fairly useful.

  • Multiple. Locally I have Timeshift doing btrfs snapshots every so often. This is mostly to roll back to a snapshot if something breaks. I’ve never had to use it (and probably should).

    I use Pika backup every once in a while for a local backup to an external drive. Mostly because it’s easy to restore quickly.

    I have duplicacy doing backups to a cloud provider. I used to use duplicati for this, and it was fine - although I didn’t like that it seems to be forever in beta. I like that duplicacy can do deduplication between backups of different machines which most other solutions I’ve seen cannot. I like its selection of cloud providers vs Borg/Vorta and some others.

  • Yote.zip ( yote_zip@pawb.social ) 
    link
    fedilink
    arrow-up
    4
    ·
    3 years ago

    I’ve used borg for a while and like it a lot. I would say your best option for pure linux is borg+borgmatic/vorta just because borg is battle-tested.

    If you run any other OSs and don’t mind a relative newcomer, I’ve found kopia to be easy to recommend to my windows friends. At this point kopia has been around long enough (~4 years of actual beta) that I think it’s safe to trust its integrity with personal data. It has all the important features from borg in a cross-platform solution, so it’s also a viable alternative for borg on linux if you don’t like borg’s frontends for whatever reason.