<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Disaster-Recovery on Mikolaj Karebski - Engineering Notes</title><link>https://blog.karebski.dev/tags/disaster-recovery/</link><description>Recent content in Disaster-Recovery on Mikolaj Karebski - Engineering Notes</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.karebski.dev/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Is Self-Hosting Hard?</title><link>https://blog.karebski.dev/posts/why-is-self-hosting-hard/</link><pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.karebski.dev/posts/why-is-self-hosting-hard/</guid><description>Why Is Self-Hosting Hard? Around a year and a half ago, I started looking into self-hosting my own infrastructure: an old laptop with 8 CPU cores and 32 GB of RAM. I wanted to run self-hosted apps to limit my data exposure to third-party companies and truly own my data, such as photos and passwords.
This felt like a natural next step after getting into homelabbing. Then something really bad happened: the hard drive in my homelab machine died.</description></item></channel></rss>