<?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 LoveIt</title><link>https://1water1.top/categories/high-availability/</link><description>Recent content in High Availability on LoveIt</description><generator>Hugo</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 29 Dec 2025 14:20:14 +0800</lastBuildDate><atom:link href="https://1water1.top/categories/high-availability/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Keepalived + Nginx Dual-Master HA Cluster from Scratch (Ubuntu 24.04)</title><link>https://1water1.top/building-keepalived-nginx-dual-master-ha-cluster/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://1water1.top/building-keepalived-nginx-dual-master-ha-cluster/</guid><description>&lt;h1 id="building-a-keepalived--nginx-dual-master-ha-cluster-from-scratch-ubuntu-2404">Building a Keepalived + Nginx Dual-Master HA Cluster from Scratch (Ubuntu 24.04)&lt;/h1>
&lt;blockquote>
&lt;p>&lt;strong>Preface&lt;/strong>:
I recently grabbed a domain for just a dollar and decided to tinker with server high availability architectures.
In a production environment, a single point of failure (SPOF) is a DevOps nightmare. Today, I&amp;rsquo;m documenting how I used Keepalived to implement a &lt;strong>Dual-Master (Active-Active)&lt;/strong> architecture.&lt;/p>
&lt;p>&lt;strong>Goal&lt;/strong>: Two servers acting as backups for each other. Normally, each handles one VIP (Virtual IP). If one server fails, the other instantly takes over all traffic!&lt;/p></description></item></channel></rss>