TrueNAS¶
my NAS runs TrueNAS, outside the proxmox cluster. it holds the backups, and because it does not depend on ceph, losing the cluster does not take the backups with it.
it runs on bare metal. for about a year before that it was a VM on its own single proxmox host, with every drive passed through to it over PCIe. that setup is kept for information in virtualized on proxmox.
what runs on it that the rest of these docs care about:
- proxmox backup server, in a TrueNAS container with its datastore on a dataset on the big pool. vm and cephfs backups land here, see backups
- S3 from Versity Gateway, for things that know how to back themselves up to S3, like portainer
- portainer stacks from git: the arr stack, frigate, glances and the dozzle agent, see truenas1
- catalog and custom apps, see apps
PBS and S3 are on the same box. the PBS datastore is also copied to azure every day, encrypted, see tasks and scripts. S3 has no copy off the box.
pools¶
| pool | used for |
|---|---|
fast |
small pool: the apps dataset, and app config under fast/configs/<app> |
rust |
big pool: media, backups, S3 buckets |
how it is put together¶
- hardware and base install: the board, the accelerators, the pools and how the network and identity are set up
- fan tuning: each fan on the sensor that matches what it cools, and what the box does under load
- system extensions: how drivers the base image does not ship get added, and survive a reboot
- storage and snapshots: dataset layout, and the rule that stopped a snapshot holding half a pool
- apps: what runs as a catalog app, where its storage goes, and the portainer agent
- frigate: the NVR, four accelerators, and why it is not an app
- containers: the PBS system container
- boot environments: making a rollback target, and protecting it so it survives the update you made it for
the app gotchas are at the end of apps, symptom first.