Most have developed abstractions to reduce platform and service specific dependency:

https://github.com/rclone/rclone

From a maintenance perspective, one must not assume a NAS is a backup, but rather a high-bandwidth local/VPN file share.

* maids unplug equipment to vacuum offices (yes, this does really happen.)

* drives fail eventually, bit-rot is a thing, and filesystems evolve over time

* hardware specific features will always become a problem eventually. No one will check a degraded RAID/ZFS setup without service telemetry.

Practical options:

* sshfs + JBOD mount is fine for most home win11/bsd/linux/macOS/iOS/android users, as simple things have less failure modes and less time-cost to repair.

* fault tolerant systems like CephFS are usually too complex for home users. However, https://www.45drives.com offers a support option for small offices.

* ZFS has a lot of tradeoffs, and most people don't use the better key features (auto-snap-shotting and docker/VM deduplication.) In some cases even F2FS will also work fine, and probably last a bit longer with consumer flash drives.

* I agree the IT support issue with distros like TrueNAS or openmediavault becomes a popularity contest over what features are supported long-term.

It is often better to use a generic OpenBSD or Debian OS installation, and run the rclone network share abstractions on PC/Mac clients. Android and iPhone both have sftp clients for auto media backups over router VPN as well..

Lightning always wins every argument, an offsite VPN to remote file-backup is usually wise. =3