For those of you running Unraid and backing up their data to Backblaze, how are you doing it?

I’ve been playing a bit with KopiaUI but what is the easiest and most straight forward way?

Bonus points if I can have the same “client/software/utility” backup data from non-servers (Windows, macOS and Linux) in my network to said Unraid server.

I don’t want to complicate the setup with a bunch of dependencies and things that would make the recovery process long and tedious or require in-depth knowledge to use it for the recovery process.

To recap:

Workstations/laptop > back up data with what? > Unraid

Unraid > back up data with what? > Backblaze

  • lal309@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Mind sharing the script (without the sensitive data)?

    I haven’t taken the plunge into rclone because of the scripting part of the equation. Just not great at bash.

    • Scrubbles@poptalk.scrubbles.tech
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      It’s pretty self run, if you’re a bit nervous, try making a folder locally on your workstation and try syncing with backblaze, just to get a feel for it. We all do a few test runs first anyway. Essentially you’ll need to

      1. Install rclone
      2. run rclone config, this will guide you step by step through adding a remote, adding credentials, etc, there’s a full guide here
      3. Try running a copy job for your test folder. It’ll be something like rclone copy /path/to/local/folder remotenameyoucreated:/

      Then go check and see if it showed up in back blaze. Play with some of the flags, like maybe you want -v so it’ll print out everything it does. During testing --dry-run can be a lifesaver.

      One big caveat, make sure you read the manual on the difference between rclone copy and rclone sync, make sure you understand both before choosing on one of them.

      I’m purposely leaving out my script because I think if you’re getting started in scripting you should start small. There’s no big script that will apply to every system. Just try copying one directory to backblaze first on your workstation, then try another, try adding those to a script and running them as a script. Mine really did start as

      #! /bin/bash
      rclone copy /mnt/user/myshare myremote:/myshare
      

      It’ll just grow with time as you add more to it, add caveats, add rules, etc. Our labs are evolving for sure, there’s no silver bullet answer. Good luck, good testing, and ping back here if you have any other questions!

      • lal309@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        My fault! This is exactly what I was going to do as I’m unfamiliar with rclone. My comment about the script was to see how to do checks to make sure the remote is actually available before trying, how to make sure the job ran successfully, how to send a notification upon success/failure, etc.

        I’m pretty novice at bash but I know other languages very well. Concepts apply more or less the same across languages, the only thing that changes in most cases is syntax.

        Anyways, good write up and I appreciate your feedback.