sanoid VS pyznap

I’m on the other end of the spectrum. I like knowing the flags and settings I use to create the pools.

For snapshots and replication take a look at sanoid (https://github.com/jimsalterjrs/sanoid).

I use a combo of PBS and ZFS with Sanoid. The ZFS snapshots are nice because you define it all in a config file with frequent, hourly, daily, weekly, monthly snaps retained however you want. Importantly I use that on the root pool as well as my data pools. With PBS I have a custom retention config and have it backing up VMs and LXCs every couple hours. The PBS dedupe functionality makes it possible to keep full backups going back ages with minimal storage consumption, just the changed blocks. PBS is running inside a VM yes, but it’s storage is on another pool.

[3] https://github.com/jimsalterjrs/sanoid/

No, it's written by the developer of Sanoid and Syncoid. The foremost open source ZFS snapshotting tool. He contributes on this sub all the time.

Hi there! Not so much to answer your questions, but are you aware of Sanoid and syncoid? It does backup and remote Sync in the most seamless way. Perhaps this would solve some of your concerns...

Sanoid/syncoids been mentioned but honestly for once a week learning by doing . Pyznap also excellent when you want to automate. https://github.com/yboetz/pyznap

In contrast, zfs snapshots are immutable, and thus anything short of a hardware failure can be addressed with a simple zfs rollback command. This includes deliberate, accidental, and malicious actions. They can also be automated (I personally use pyznap but syncoid is also quite popular), creating what is effectively an incremental backup. I maintain - for each dataset - 24 hourly, 7 daily, 6 monthly, and 1 yearly snapshot. Additionally, I have a wholly separate server that wakes up once a day to ingest these snapshots via zfs send/recv, so even if I made a horrible mistake or suffered a catastrophic hardware failure, I could completely restore from the other server. This last point brings snapshots firmly into the realm of backups, IMO.

Another favorite option is Pyznap, which is python based and originally created to have have a few features and changes compared to sanoid. The author is also active here on reddit. I and not sure what the differences are anymore, it'll come down to trying them and preference.

I have two Supermicro X9 2Us, each with Proxmox. One has allegedly existed solely as a backup target, which wakes up daily to ingest ZFS snapshots using pyznap. Unfortunately, for reasons which are unclear, this particular node doesn't always like to see its boot device, which is an NVMe drive. It's the exact same board as my primary, with the exact same modified BIOS to allow booting from NVMe. It usually takes 2-3 cycles before it'll see it and boot.

I have two nearly identical systems, both running Proxmox, with Debian VMs. One is a backup, which (once this is worked out) will wake up daily to ingest incremental backups. I'm using pyznap to handle the backup strategy.

https://github.com/yboetz/pyznap/issues/1#issuecomment-351015432