‹ BackHN Continuity

Thread

Backups Aren't Simple

359 points · 225 comments · afilipovski

  1. Helmut10001 · · focus · HN ↗
    I really like ZFS snapshots with offsite pull-mode sync using Jim Salter's sanoid/syncoid [1]. ZFS is the base for all OS/filesystems on top of it. If you have a good system for organizing ZFS datasets, and separating ephemeral from persistent data (e.g. [2]), then this is 90% of the backup requirements already fullfilled.

        [1]: https://github.com/jimsalterjrs/sanoid
        [2]: https://du.nkel.dev/blog/2026-05-16_rootless_docker_virtiofs_proxmox/
    1. zenoprax · · focus · HN ↗
      Thanks for the second link - looks interesting.

      I have an old and loud 16-bay server that boots every 7 days or so if no one is home, `syncoid there here`, and shuts off. I'll get pinged by uptimerobot once in a while if it's overdue and I'll get a notification if a pool is unhealthy or reaching capacity (`sanoid --health` I think). Otherwise I forget I even have it set up.

      Automated cold backups are great peace-of-mind.

      1. Helmut10001 · · focus · HN ↗
        Exactly! My offsite Backup box boots using a Shelly Plug S set on timer; it doesn't need to unlock the enrypted ZFS datasets because I use zfs sync snapshots in raw mode (-R). After the zfs scrupt, the box sends an email to me and shuts down. Next week: Repeat.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.