<?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>vReference &#187; HA</title>
	<atom:link href="http://www.vReference.com/tag/ha/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vReference.com</link>
	<description>guides, links and news for VMware and virtualization technologies</description>
	<lastBuildDate>Mon, 19 Jul 2010 04:10:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>n+1 is hogwash!</title>
		<link>http://www.vReference.com/2010/02/15/n1-is-hogwash/</link>
		<comments>http://www.vReference.com/2010/02/15/n1-is-hogwash/#comments</comments>
		<pubDate>Mon, 15 Feb 2010 15:03:31 +0000</pubDate>
		<dc:creator>Forbes Guthrie</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[HA]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere4]]></category>

		<guid isPermaLink="false">http://www.vReference.com/?p=687</guid>
		<description><![CDATA[Too frequently I hear the expression n+1 as a model for ESX clusters to provide High Availability.  If you EVER expect to patch ESX servers without VM downtime then you need at least(†) n+2.  When running your clusters to only n+1, you can never safely put one of...<p>=====
<a href="http://www.vReference.com/2010/02/15/n1-is-hogwash/">n+1 is hogwash!</a>  originally posted by Forbes Guthrie on <a href="http://www.vReference.com">vReference</a>.
Subscribe to my <a href="http://feeds2.feedburner.com/vreference">RSS feed</a> for all the latest updates.</p>



Related posts:<ol><li><a href='http://www.vReference.com/2008/07/10/when-your-mind-goes-blank/' rel='bookmark' title='Permanent Link: When your mind goes blank'>When your mind goes blank</a></li>
<li><a href='http://www.vReference.com/2008/01/25/corrupted-vmdk-and-vmsd-files/' rel='bookmark' title='Permanent Link: Corrupted vmdk and vmsd files'>Corrupted vmdk and vmsd files</a></li>
<li><a href='http://www.vReference.com/2009/06/18/mscs-confusion/' rel='bookmark' title='Permanent Link: MSCS confusion'>MSCS confusion</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>Too frequently I hear the expression <em>n+1</em> as a model for ESX clusters to provide High Availability.  If you EVER expect to patch ESX servers without VM downtime then you need at least(†) n+2.  When running your clusters to only n+1, you can never safely put one of your hosts in Maintenance Mode; not if High Availability is important to you.</p>
<p><a href="http://www.vReference.com/wp-content/uploads/HA_failover.png"><img class="aligncenter size-full wp-image-689" title="HA failover" src="http://www.vReference.com/wp-content/uploads/HA_failover.png" alt="" width="413" height="113" /></a></p>
<p>Footnote: If you don&#8217;t understand the importance of HA slot sizes, <a href="http://www.yellow-bricks.com/vmware-high-availability-deepdiv/">go learn</a>.</p>
<p>=====
<a href="http://www.vReference.com/2010/02/15/n1-is-hogwash/">n+1 is hogwash!</a>  originally posted by Forbes Guthrie on <a href="http://www.vReference.com">vReference</a>.
Subscribe to my <a href="http://feeds2.feedburner.com/vreference">RSS feed</a> for all the latest updates.</p>


<p>Related posts:<ol><li><a href='http://www.vReference.com/2008/07/10/when-your-mind-goes-blank/' rel='bookmark' title='Permanent Link: When your mind goes blank'>When your mind goes blank</a></li>
<li><a href='http://www.vReference.com/2008/01/25/corrupted-vmdk-and-vmsd-files/' rel='bookmark' title='Permanent Link: Corrupted vmdk and vmsd files'>Corrupted vmdk and vmsd files</a></li>
<li><a href='http://www.vReference.com/2009/06/18/mscs-confusion/' rel='bookmark' title='Permanent Link: MSCS confusion'>MSCS confusion</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.vReference.com/2010/02/15/n1-is-hogwash/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>VMworld: HA</title>
		<link>http://www.vReference.com/2009/09/05/vmworld-ha/</link>
		<comments>http://www.vReference.com/2009/09/05/vmworld-ha/#comments</comments>
		<pubDate>Sun, 06 Sep 2009 06:56:49 +0000</pubDate>
		<dc:creator>Forbes Guthrie</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[VMworld 2009]]></category>
		<category><![CDATA[HA]]></category>
		<category><![CDATA[VMworld]]></category>

		<guid isPermaLink="false">http://www.vReference.com/?p=303</guid>
		<description><![CDATA[While attending the HA: Internals and Best Practices session (BC3197) on Tuesday afternoon, I learned something new about HA&#8217;s VM health monitoring.  With a cluster&#8217;s HA, you can set it to monitor the health of your VMs and have them automatically restart if it detects...<p>=====
<a href="http://www.vReference.com/2009/09/05/vmworld-ha/">VMworld: HA</a>  originally posted by Forbes Guthrie on <a href="http://www.vReference.com">vReference</a>.
Subscribe to my <a href="http://feeds2.feedburner.com/vreference">RSS feed</a> for all the latest updates.</p>



Related posts:<ol><li><a href='http://www.vReference.com/2009/08/25/dear-vmworld-part-2/' rel='bookmark' title='Permanent Link: Dear VMworld (part 2)'>Dear VMworld (part 2)</a></li>
<li><a href='http://www.vReference.com/2009/09/10/vmworld-networking-deep-dive/' rel='bookmark' title='Permanent Link: VMworld: Networking Deep Dive'>VMworld: Networking Deep Dive</a></li>
<li><a href='http://www.vReference.com/2009/09/01/vmworld-host-profiles/' rel='bookmark' title='Permanent Link: VMworld: Host Profiles'>VMworld: Host Profiles</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>While attending the HA: Internals and Best Practices session (BC3197) on Tuesday afternoon, I learned something new about HA&#8217;s VM health monitoring.  With a cluster&#8217;s HA, you can set it to monitor the health of your VMs and have them automatically restart if it detects an OS hang-up.  To do this it uses a heartbeat from the Guest&#8217;s VMware tools.</p>
<p>The cool thing I never knew before is a screenshot of the VM&#8217;s console is taken before it is reset, with up to 10 being saved (in the same directory as the vmx file).  So when you are trying to troubleshoot the issue that caused the VM to become unresponsive, you should have a screenshot of the BSOD or any onscreen messages.  Cool.</p>
<p>=====
<a href="http://www.vReference.com/2009/09/05/vmworld-ha/">VMworld: HA</a>  originally posted by Forbes Guthrie on <a href="http://www.vReference.com">vReference</a>.
Subscribe to my <a href="http://feeds2.feedburner.com/vreference">RSS feed</a> for all the latest updates.</p>


<p>Related posts:<ol><li><a href='http://www.vReference.com/2009/08/25/dear-vmworld-part-2/' rel='bookmark' title='Permanent Link: Dear VMworld (part 2)'>Dear VMworld (part 2)</a></li>
<li><a href='http://www.vReference.com/2009/09/10/vmworld-networking-deep-dive/' rel='bookmark' title='Permanent Link: VMworld: Networking Deep Dive'>VMworld: Networking Deep Dive</a></li>
<li><a href='http://www.vReference.com/2009/09/01/vmworld-host-profiles/' rel='bookmark' title='Permanent Link: VMworld: Host Profiles'>VMworld: Host Profiles</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.vReference.com/2009/09/05/vmworld-ha/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
