<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>backups on 'That' badly designed HomeLab</title><link>https://forcebyte.github.io/tags/backups/</link><description>Recent content in backups on 'That' badly designed HomeLab</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Firehaven</copyright><lastBuildDate>Tue, 20 Oct 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://forcebyte.github.io/tags/backups/index.xml" rel="self" type="application/rss+xml"/><item><title>ShikataLab - Backups: a Bucket, a Database Filesystem, and a Binlog Surprise</title><link>https://forcebyte.github.io/posts/2026-20-10-shikata-backups/</link><pubDate>Tue, 20 Oct 2026 09:00:00 -0400</pubDate><guid>https://forcebyte.github.io/posts/2026-20-10-shikata-backups/</guid><description>For a long time, my homelab backup strategy was &amp;ldquo;nothing here is irreplaceable,&amp;rdquo; which is a fine strategy right up until the day it isn&amp;rsquo;t. In my case the day came during a routine rebuild: a PersistentVolumeClaim got recreated, the volume underneath it went away with it, and my web analytics database — years of history — was just gone. Kubernetes defaults did exactly what they&amp;rsquo;re documented to do. The PVC had a Delete reclaim policy, the storage class agreed, and the data left.</description></item></channel></rss>