I was using straight filesystem backups for a while, but I knew they could be inconsistent. Since then, I've setup https://github.com/prodrigestivill/docker-postgres-backup-lo..., which regularly dumps a snapshot to the filesystem, which regular filesystem backups can consume. The README has restore examples, too
I haven't needed to tune selfhosted databases. They do fine for low load on cheap hardware from 10 years ago.
Getting my backup infrastructure to behave they way I'd want with filesystem snapshot (e.g. zfs or btrfs snapshot) was not trivial. (I think the hurdle was my particularity about the path prefix that was getting backed up.) write once pg_dumps could still have race conditions, but considerably fewer.
So, if you're using filesystem snapshots as source of backups for database, then I agree, you _should_ be good. the regular pgdumps is a workaround for other cases for me.
I have a very old rotary phone that you “dial” how bright to make the lights. esp8266 detects dial pulses, sends mqtt message to home assistant, home assistant sets zigbee can/recessed lights to requested setting
I've had to force my Hue bulb into zigbee pairing mode by holding a Hue dimmer switch very close, then pressing and holding the on and off buttons until the light starts to flash and stops flashing, then releasing the on/off buttons.
I keep 2x ~150 USD machines at home; 1 active, 1 cold spare. Current active is Dell 3020 w/ 4th gen i5-4590 3.3GHZ Quad-Core, 8 GB RAM. It has been enough for nextcloud, jellyfin, home assistant, backups. I think it averages about 30w
I haven't needed to tune selfhosted databases. They do fine for low load on cheap hardware from 10 years ago.