<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High-Availability on Ivan Luminaria</title><link>https://ivanluminaria.com/en/tags/high-availability/</link><description>Recent content in High-Availability on Ivan Luminaria</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 17 Feb 2026 08:03:00 +0100</lastBuildDate><atom:link href="https://ivanluminaria.com/en/tags/high-availability/index.xml" rel="self" type="application/rss+xml"/><item><title>Galera Cluster with 3 nodes: how I solved a MySQL availability problem</title><link>https://ivanluminaria.com/en/posts/mysql/galera-cluster-3-nodi/</link><pubDate>Tue, 17 Feb 2026 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/mysql/galera-cluster-3-nodi/</guid><description>&lt;p&gt;The ticket was laconic, as it often is when the problem is serious: &amp;ldquo;The database went down again. The application is stopped. Third time in two months.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The client had a MariaDB on a single Linux server — a business management application used by about two hundred internal users, with load spikes during end-of-month accounting closures. Every time the server had a problem — a disk slowing down, a system update requiring a reboot, a process consuming all the RAM — the database crashed and with it the entire business operations.&lt;/p&gt;</description></item><item><title>From Single Instance to Data Guard: The Day the CEO Understood DR</title><link>https://ivanluminaria.com/en/posts/oracle/oracle-data-guard/</link><pubDate>Tue, 16 Dec 2025 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/oracle/oracle-data-guard/</guid><description>&lt;p&gt;The client was a mid-sized insurance company. Three hundred employees, an in-house management application running on Oracle 19c, a single physical server in the ground-floor server room. No replica. No standby. No disaster recovery plan.&lt;/p&gt;
&lt;p&gt;For five years everything had worked. And when things work, nobody wants to spend money protecting against problems they&amp;rsquo;ve never seen.&lt;/p&gt;
&lt;h2 id="the-day-everything-stopped" class="relative group"&gt;The day everything stopped &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#the-day-everything-stopped" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;On a Wednesday morning in November, at 8:47 AM, the primary data group&amp;rsquo;s disk suffered a hardware failure. Not a logical error, not a recoverable corruption. A physical failure. The RAID controller lost two disks simultaneously — one had been degraded for weeks without anyone noticing, the other gave out suddenly.&lt;/p&gt;</description></item></channel></rss>