![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.hogru.ch/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2F8286e071-7449-4413-a084-1eb5242e2cf4.png)
Immutable Nixos. My entire server deployment from partitioning to config is stored in git on all my machines.
Every time I boot all runtime changes are “wiped”, which is really just BTRFS subvolume swapping.
Persistence is possible, but I’m forced to deal with it otherwise it will get wiped on boot.
I use LVM for mirrored volumes for local redundancy.
My persisted volumes are backed up automatically to B2 Backblaze using rclone. I don’t backup everything. Stuff I can download again are skipped for example. I don’t have anything currently that requires putting a process in “maint mode” like a database getting corrupt if I backup while its being written to. When I did, I’d either script gracefully shutting down the process or use any export functionality if the process supported it.
https://www.goodreads.com/book/show/1098624.When_I_Say_No_I_Feel_Guilty
Its dated and probably misogynistic given the period, but when I did read it many many years ago, the broken record technique is probably the one thing I do remember. It also had some role play dialog for how others may try and break the loop. I found it helpful at the time.
I think I read/heard something similar in one of the Love and Logic parenting books/ebooks. “Maybe so, but <repeat assertion>” comes to mind. Acknowledge the statement that attempts to break the loop, don’t add any new information, and repeat the assertion.