• qjkxbmwvz@startrek.website
    link
    fedilink
    arrow-up
    3
    ·
    2 days ago

    Yeah. My solution is raspberry pi w/WireGuard + HDD at inlaws. Initial backup was done locally, nightly backups rsync’d over (I don’t generate a ton of data, so it’s mostly just photos from my phone).

      • qjkxbmwvz@startrek.website
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        We “only” have ~35Mbps upload, but that’s plenty since the initial backup was the only large transfer. Daily backup transfers are generally pretty small for me.

        But getting the initial transfer done locally was definitely important for my use case!

          • ferret@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            6
            ·
            2 days ago

            You probably don’t generate more than 4 megabits of backup-worthy data on average every second

            • qjkxbmwvz@startrek.website
              link
              fedilink
              arrow-up
              2
              ·
              1 day ago

              Exactly — this is ~10GB every 6 hours (which is probably a reasonable amount of time to run a backup while not interfering with active Internet use).

              Basically the only backup-worthy content I generate is casual photos and videos, and these are nowhere near that size (Immich database backups also take up a bit but I could certainly be smarter about how I handle these backups).