<?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 F. Latini - IT Engineer</title><link>https://latini.dev/tags/disaster-recovery/</link><description>Recent content in Disaster-Recovery on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 19 Nov 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>Could You Rebuild Your Platform From Nothing?</title><link>https://latini.dev/posts/could-you-rebuild-your-platform-from-nothing/</link><pubDate>Thu, 19 Nov 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/could-you-rebuild-your-platform-from-nothing/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - Every service in your estate has a disaster recovery story, and almost all of them begin with the same sentence: &amp;ldquo;redeploy it through the platform&amp;rdquo;. The platform itself usually has no such story. It was assembled over two or three years, partly from code and partly by hand, and it is full of quiet loops: the pipeline deploys the pipeline, the secret store is unsealed with keys kept in the secret store, the recovery runbook lives on a wiki hosted on the cluster it describes. Nobody has ever rebuilt it from an empty account, so nobody knows whether they could, or how long it would take. The fix is not a two-hundred-page DR plan. It is a map of the cycles with a named break point for each, a deliberately small &amp;ldquo;layer zero&amp;rdquo; that lives outside everything it bootstraps, a written bootstrap order, and a timed rebuild drill that proves the whole thing works before the day you need it.&lt;/p&gt;</description></item></channel></rss>