<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Cluster with 2-Nodes only Archives - ESX Virtualization</title>
	<atom:link href="https://www.vladan.fr/tag/cluster-with-2-nodes-only/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vladan.fr/tag/cluster-with-2-nodes-only/</link>
	<description>VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....</description>
	<lastBuildDate>Thu, 27 Apr 2023 09:42:25 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Cluster with 2-Nodes only &#8211; How about quorum?</title>
		<link>https://www.vladan.fr/cluster-with-2-nodes-only-how-about-quorum/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Thu, 27 Apr 2023 09:42:25 +0000</pubDate>
				<category><![CDATA[Server Virtualization]]></category>
		<category><![CDATA[Cluster with 2-Nodes only]]></category>
		<guid isPermaLink="false">https://www.vladan.fr/?p=231586</guid>

					<description><![CDATA[<p>If you're thinking about 2-Node cluster configuration, one of the challenges might be the question might be on how split-brain scenarios are handled? To remind you, a split-brain scenario is when your cluster has a node failure or there is a network failure between two nodes, and then both systems are back online again. Which [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/cluster-with-2-nodes-only-how-about-quorum/">Cluster with 2-Nodes only &#8211; How about quorum?</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
