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.

  • Max-P@lemmy.max-p.me
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    14 hours 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.