<?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 Cloudowski DevOps Expert</title><link>https://555c327d.hugo-coudowski-website.pages.dev/tags/disaster-recovery/</link><description>Recent content in Disaster-recovery on Cloudowski DevOps Expert</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://555c327d.hugo-coudowski-website.pages.dev/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>What is Continuous Data Recovery Testing</title><link>https://555c327d.hugo-coudowski-website.pages.dev/articles/what-is-continuous-data-recovery-testing/</link><pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate><guid>https://555c327d.hugo-coudowski-website.pages.dev/articles/what-is-continuous-data-recovery-testing/</guid><description>&lt;p>Once you follow the practices that I preach about defining and maintaining your whole platform with code, you&amp;rsquo;re simplifying and speeding up the recovery process. It&amp;rsquo;s a huge gain for an organization that prepares for the worst. It&amp;rsquo;s part of the &amp;ldquo;Design for Failure&amp;rdquo; principle that has been a part of best practices within the platform architects&amp;rsquo; community.&lt;/p></description></item></channel></rss>