I recently replaced an ancient laptop with a slightly less ancient one.

  • host for backups for three other machines
  • serve files I don’t necessarily need on the new machine
  • relatively lightweight - “server” is ~15 years old
  • relatively simple - I’d rather not manage a dozen docker containers.
  • internal-facing
  • does NOT need to handle Android and friends. I can use sync-thing for that if I need to.

Left to my own devices I’d probably rsync for 90% of that, but I’d like to try something a little more pointy-clicky or at least transparent in my dotage.

Edit: Not SAMBA (I freaking hate trying to make that work)

Edit2: for the young’uns: NFS (linux “network filesystem”)

Edit 3: LAN only. I may set up a VPN connection one day but it’s not currently a priority. (edited post to reflect questions)

Last Edit: thanks, friends, for this discussion! I think based on this I’ll at least start with NFS + my existing backups system (Mint’s thing, which is I think just a gui in front of rcync). May play w/ modern SAMBA if I have extra time.

Ill continue to read the replies though - some interesting ideas.

  • loweffortname@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    I think a reasonable quorum already said this, but NFS is still good. My only complaint is it isn’t quite as user-mountable as some other systems.

    So…I know you said no SAMBA, but SAMBA 4 really isn’t bad any more. At least, not nearly as shit as it was.

    If you want a easily mountable filesystem for users (e.g. network discovery/etc.) it’s pretty tolerable.

  • graycube@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    I’d use an s3 bucket with s3fs. Since you want to host it yourself, Minio is the open-source tool to use instead of s3.

      • Brkdncr@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        NFS works, but http was designed for shitty internet. Keep that in mind. Owncloud or similar might be a good idea.

  • cmnybo@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    NFS is the best option if you only need to access the shared drives over your LAN. If you want to mount them over the internet, there’s SSHFS.

    • non_burglar@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      15 days ago

      I agree, NFS is eazy peazy, livin greazy.

      I have an old ds211j synology for backup. I just can’t bring myself to replace it, it still works. However, it doesn’t support zfs. I wish I could get another Linux running on this thing.

      However, NFS does work on it and is so simple and easy to lock down, it works in a ton of corner cases like mine.

      • Antithetical@lemmy.deedium.nl
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        NFS is easy as long as you use very basic access control. When you want NFSv4 with Kerberos auth you’re entering a world of pain and tears.

      • needanke@feddit.org
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        Afaik Synology supports Btrfs which I honestly prefer at this point if you don’t need filesystem based encryption or professionall scaling and caching features.

        • non_burglar@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          15 days ago

          The ds211j is on synology DSM 6, which is ancient. I’ll look again, but I don’t think it supports btrfs.

      • cmnybo@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        You can use NFS over the internet, but it will be a lot more work to secure it. It was intended for use over a LAN and performance may not be great over the internet, especially with high latency or packet loss.

    • BonkTheAnnoyed@lemmy.blahaj.zoneOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      15 days ago

      See, this is interesting. I’m out here looking for the new shiny easy button, but what I’m hearing is “the old config-file based thing works really well. ain’t broken, etc.”

      I may give that a swing and see.

      • curbstickle@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        I’m at the same age - just to mention, samba is nowhere near the horror show it used to be. That said, I use NFS for my Debian boxes and mac mini build box to hit my NAS, samba for the windows laptop.

        • roofuskit@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          15 days ago

          Yeah, Samba has come a long way. I run a Linux based server but all clients are Windows or Android so it just makes sense to run SMB shares instead of NFS.

          • WhyJiffie@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            15 days ago

            you and perhaps @curbstickle@lemmy.dbzer0.com, may I ask if you use samba with portable devices, like laptops?

            I do and my experience is that programs that try to access it when I don’t have network access tend to freeze, including my desktop environment, but any file managers too if I click the wrong place by accident. but it occurs enough without user action too.
            oh and it breaks all machines at once if the server or network is down. which is rare but very annoying.

            did you experience this too? do you have some advice? is SMB just unsuitable for this?

            honestly I would prefer if the cifs driver would keep track of last successful communication, and if it was long ago instantly fail all accesses. without unmounting so that open directories and file handles keep being valid.
            and if all software on this world wouldn’t behave as if they were doing IO on the main thread. honestly this went smoother with windows clients but I’m not going back.

          • ImgurRefugee114@reddthat.com
            link
            fedilink
            English
            arrow-up
            0
            ·
            15 days ago

            I’ve always had weird issues with SMB like ghost files, issues with case sensitivity (zfs pool), it dropping out and me having to reboot to re-establish the connection… Since switching to Linux and using NFS, it’s been almost indistinguishable from a native drive for my casual use (including using a ssd pool as a steam library…)

            • roofuskit@lemmy.world
              link
              fedilink
              English
              arrow-up
              0
              ·
              15 days ago

              I can definitely say I’m the past I had similar experiences. I haven’t really had any problems with SMB in the last 5 years that I can recall. It really was a shit show back in the day, but it’s been rock solid for me anyway.

        • Bakkoda@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          15 days ago

          I’ve run Proxmox hosts with smb shares for literally a decade without issue. Performance is line speed now. Only issues I’ve ever had were operator error and that was a long time ago. SMB 3 works great.

    • fmstrat@lemmy.nowsci.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      15 days ago

      My one change: I do SSHFS over LAN, because of guest machines and sniffing potential.

      I do NFS on direct wire or on a confidently set up VLAN (maybe).

    • Hawke@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      15 days ago

      Isn’t nfs pretty much completely insecure unless you turn on nfs4 with Kerberos? The fact that that is such a pain in the ass is what keeps me from it. It is fine for read-only though.

      • nesc@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        It is, but nfsv3 is extremely easy to configure. You need to edit 1 line in 1 file and it’s ready to go.

      • undefined@lemmy.hogru.ch
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        15 days ago

        If you’ve got Tailscale it’ll build WireGuard tunnels directly over the LAN: I actually do this with Samba for Time Machine backups on macOS.

        Obviously the big bonus is being able to do the same over the internet without the gaping security holes.

        (I used to use split DNS so that my LAN’s router’s DNS server returned the LAN IP, and Tailscale’s DNS server returned the Tailscale IP. But because I’m a privacy geek I decided to make it Tailscale-only.)

  • Max-P@lemmy.max-p.me
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    For all its flaws and mess, NFS is still pretty good and used in production.

    I still use NFS to file share to my VMs because it still significantly outperforms virtiofs, and obviously network is a local bridge so latency is non-existent.

    The thing with rsync is that it’s designed to quickly compute the least amount of data transfer to sync over a remote (possibly high latency) link. So when it comes to backups, it’s literally designed to do that easily.

    The only cool new alternative I can think of is, use btrfs or ZFS and btrfs/zfs send | ssh backup btrfs/zfs recv which is the most efficient and reliable way to backup, because the filesystem is aware of exactly what changed and can send exactly that set of changes. And obviously all special attributes are carried over, hardlinks, ACLs, SELinux contexts, etc.

    The problem with backups over any kind of network share is that if you’re gonna use rsync anyway, the latency will be horrible and take forever.

    Of course you can also mix multiple things: rsync laptop to server periodically, then mount the server’s backup directory locally so you can easily browse and access older stuff.

  • RedEye FlightControl@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    TrueNas is pretty top notch and offers a variety of storage and protocol options. If you’re at all familiar with Linux style OS, it should be pretty easy to work with. Setting up storage comes with a little bit of a learning curve, but it’s not too bad. This SAN/NAS OS is polished, performant, and extensible. If you’re not planning on using SMB or Samba, you can most certainly use NFS, or iSCSI if that’s your thing.

  • Frezik@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    Everyone forgets about WebDAV.

    It’s a little jank, but it does work on Windows. If you copy a file in, it doesn’t show up in the file manager until you refresh. But it works.

    It’s also multithreaded, which isn’t the case for SMB. This is especially good if you host it on SSDs.

  • 9tr6gyp3@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    15 days ago

    Check out SyncThing, which can sync a folder of your choice across all 3 devices

    [edit] oops, just saw you don’t plan on using it

    In that case, if you use KDE, you can use Dolphin to set up network drives to your local network machines through SSH

    • 486@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      15 days ago

      Syncthing is neat, but you shouldn’t consider it to be a backup solution. If you accidentally delete or modify a file on one machine, it’ll happily propagate that change to all other machines.

      • addie@feddit.uk
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        You can turn off “delete”, but modification is a danger, it’s true.

        Turning off delete makes it excellent for eg. backing up photographs on your phone. I’ve got it doing this from my Android to my raspberry pi, which puts them on my NAS for me. Saves losing all my pictures if I lose my phone.

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      0
      ·
      15 days ago

      I like this solution because I can have the need filled without a central server. I use old-fashioned offline backups for my low-churn, bulk data, and SyncThing for everything else to be eventually consistent everywhere.

      If my data was big enough so as to require dedicated storage though, I’d probably go with TrueNAS.

  • talkingpumpkin@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    If it’s for backup, zfs and btrfs can send incremental diffs quite efficiently (but of course you’ll have to use those on both ends).

    Otherwise, both NFS and SMB are certainly viable.

    I tried both but TBH I ended up just using SSHFS because I don’t care about becoming and NFS/SMB admin.

    NFS and SMB are easy enough to setup, but then when you try to do user-level authentication… they aren’t as easy anymore.

    Since I’m already managing SSH keys all over my machines, I feel like SSHFS makes much more sense for me.

      • tofu@lemmy.nocturnal.garden
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        It’s heavy and it doesn’t like if you tinker with the box in Non-TrueNAS ways. In the end it’s a convenient shiny gui for ZFS and NFS. But it (or ZFS) needs some RAM (minimum 8 I think), so I’m not sure about it working on your old laptop.

  • velxundussa@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    For linux only, lan only shared drive NFS is probably the easiest you’ll get, it’s made for that usecase.

    If you want more of a dropbox/onedrive/google drive experience, Syncthing is really cool too, but that’s a whole other architecture qhere you have an actual copy on all machines.