 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: VMware engineers caution IT pros: Use Fault Tolerance sparingly</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/server-virtualization/vmware-engineers-caution-it-pros-use-fault-tolerance-sparingly/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/server-virtualization/vmware-engineers-caution-it-pros-use-fault-tolerance-sparingly/</link>
	<description>A SearchServerVirtualization.com and SearchVMware.com blog</description>
	<lastBuildDate>Wed, 12 Sep 2012 17:14:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: MikeLaverick</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/vmware-engineers-caution-it-pros-use-fault-tolerance-sparingly/#comment-1588</link>
		<dc:creator>MikeLaverick</dc:creator>
		<pubDate>Thu, 14 May 2009 15:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/server-virtualization/?p=1430#comment-1588</guid>
		<description><![CDATA[I&#039;m suprised they set the value so high. Private-beta webcasts put the value more around the 10% mark. I don&#039;t think at the end of the day the overhead is perhaps the most significant limitation on FT to date. Most customers accept you don&#039;t get something for nothing when it comes to feature like VMotion, SVMotion and FT.

What will make FT tricky - is two things - the conversion of the virtual disks they already have to zeroedthick to eagerzeroedthick. The fact that FT only supports 1-vCPU when many critical systems that would suit FT are using vSMP. And last the bandwidth required for the FT Logging network - in addition to their VMotion pipes.....

The message is the product. Enable HA it protect ALL VMs in the cluster, but FT is enabled on per-VM basis...]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m suprised they set the value so high. Private-beta webcasts put the value more around the 10% mark. I don&#8217;t think at the end of the day the overhead is perhaps the most significant limitation on FT to date. Most customers accept you don&#8217;t get something for nothing when it comes to feature like VMotion, SVMotion and FT.</p>
<p>What will make FT tricky &#8211; is two things &#8211; the conversion of the virtual disks they already have to zeroedthick to eagerzeroedthick. The fact that FT only supports 1-vCPU when many critical systems that would suit FT are using vSMP. And last the bandwidth required for the FT Logging network &#8211; in addition to their VMotion pipes&#8230;..</p>
<p>The message is the product. Enable HA it protect ALL VMs in the cluster, but FT is enabled on per-VM basis&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
