-
After the wipe: six habits that changed how I run my home lab
A test deleted my home folder in ten seconds. Recovery took two days; the habits it left took longer. Freeze before you fix, reboot on purpose, back up the boring files hourly, commit everything, and give agents their own user.
-
Velero said Completed. It had backed up a RAM disk.
Velero's Kopia backup skipped my main Postgres because it used hostPath, saving only an in-memory temp volume; 13 of 17 databases had no backup anywhere. PV fixes, two OOM kills, and a byte-exact restore.
-
My first restore test reported 0 tables and 0 errors
I had checked 49 backup sets for months but never restored one. The first test restored nothing and reported success. How to test Postgres restores safely, and three ways backups and restores quietly lie.
-
Backups that lie, and the freshness alarm that catches them
My backup jobs reported OK while 13 of 17 databases had no backup, dumps were truncated and two crons had been dead for months. One freshness check over the artifacts of every backup set now catches all of it.