<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ucarp on №42</title>
    <link>https://blog.no42.org/tags/ucarp/</link>
    <description>Recent content in Ucarp on №42</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 07 Feb 2020 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.no42.org/tags/ucarp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>UCARP and High Availability</title>
      <link>https://blog.no42.org/article/ucarp-high-availability/</link>
      <pubDate>Fri, 07 Feb 2020 00:00:00 +0000</pubDate>
      <guid>https://blog.no42.org/article/ucarp-high-availability/</guid>
      <description>&lt;p&gt;If you have ever played with BSD you probably ran into &lt;a href=&#34;https://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol&#34;&gt;CARP&lt;/a&gt;.&#xA;It allows you to build a high available service which is provided by two physical servers behind a virtual shared IP address.&#xA;The CARP nodes define a master and a backup system.&#xA;A master serves the content and if the master crashes, the backup system takes over automatically the virtual IP (VIP) and the client won&amp;rsquo;t notice.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt;&#xA;You should be aware this setup will not share load and increase your network throughput.&#xA;It just used to increase availabilty and room to do maintenance without bringing your service down.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
