<rss xmlns:webfeeds="http://webfeeds.org/rss/1.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
  <atom:link href="https://nxlog.co/news-and-blog/index.xml" rel="self" type="application/rss+xml" />
  <title>Disaster recovery</title>
    <link>https://nxlog.co/news-and-blog/tags/disaster-recovery/</link>
    <description>Recent content in Disaster recovery on NXLog Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
  <lastBuildDate>Mon, 03 Aug 2026 00:00:00 +0000</lastBuildDate>
  
  <item>
    <title>Surviving a region outage: multi-region disaster recovery for NXLog Platform on AWS</title>
    <link>https://nxlog.co/news-and-blog/posts/multi-region-disaster-recovery-nxlog-platform-aws/</link>
    <pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate>
    
    <enclosure url="https://nxlog.co/news-and-blog/images/categories/deployment.webp" type="image/webp" />
    <atom:logo>https://nxlog.co/news-and-blog/images/categories/deployment.webp</atom:logo>
    
    <guid>https://nxlog.co/news-and-blog/posts/multi-region-disaster-recovery-nxlog-platform-aws/</guid>
    <description>
    
    &lt;img src=&#34;https://nxlog.co/news-and-blog/images/categories/deployment.webp&#34; width=500 /&gt;
    
    When a cloud region goes down, most teams think about their applications first. But if your log management platform goes dark, you lose more than a dashboard — you lose your audit trail, your security telemetry, and in many industries, your compliance posture. Every minute your ingestion endpoint is unreachable is a minute of blind spots you can’t get back.
The good news: if you run NXLog Platform on AWS, building a multi-region disaster recovery (DR) setup is more straightforward than you might expect.
    </description>
    
    <dc:creator><![CDATA[ João Correia ]]></dc:creator>
    
  </item>
   
  </channel>
</rss>
