<?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 Shadowfish</title><link>https://shadowfish.night-tower.net/tags/disaster-recovery/</link><description>Recent content in Disaster Recovery on Shadowfish</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 Creeping depths of the deep</copyright><lastBuildDate>Sat, 01 Aug 2026 19:00:00 +0200</lastBuildDate><atom:link href="https://shadowfish.night-tower.net/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>The Great Database Wipeout: How a Single 'DROP DATABASE' Taught Me Everything About Backups</title><link>https://shadowfish.night-tower.net/post/the-great-database-wipeout/</link><pubDate>Sat, 01 Aug 2026 19:00:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/the-great-database-wipeout/</guid><description>&lt;p&gt;There is a specific kind of cold sweat known only to software engineers and database administrators.&lt;/p&gt;
&lt;p&gt;It happens in a microsecond. You press &lt;strong&gt;Enter&lt;/strong&gt; in your terminal, expect a clean 3-millisecond query response, and instead watch the terminal freeze. You glance up at your tab title and realize with horror:&lt;/p&gt;
&lt;p&gt;You weren&amp;rsquo;t connected to &lt;code&gt;staging&lt;/code&gt;. You were connected to &lt;code&gt;production&lt;/code&gt;.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/the-great-database-wipeout/featured.jpg"/></item></channel></rss>