<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Long Distance vMotion&#8230; heading to the vCloud</title>
	<atom:link href="http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/feed/" rel="self" type="application/rss+xml" />
	<link>http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/</link>
	<description>My ramblings on the stuff that holds it all together</description>
	<lastBuildDate>Tue, 14 Feb 2012 12:29:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Geographically dispersed cluster design &#124; Arnim van Lieshout</title>
		<link>http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/#comment-1248</link>
		<dc:creator><![CDATA[Geographically dispersed cluster design &#124; Arnim van Lieshout]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 11:46:43 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/#comment-1248</guid>
		<description><![CDATA[[...] http://www.virtuallifestyle.nl/2009/09/vmworld-09-long-distance-vmotion-ta3105/ http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/ http://www.yellow-bricks.com/2009/09/21/long-distance-vmotion/ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.virtuallifestyle.nl/2009/09/vmworld-09-long-distance-vmotion-ta3105/" rel="nofollow">http://www.virtuallifestyle.nl/2009/09/vmworld-09-long-distance-vmotion-ta3105/</a> <a href="http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/" rel="nofollow">http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/</a> <a href="http://www.yellow-bricks.com/2009/09/21/long-distance-vmotion/" rel="nofollow">http://www.yellow-bricks.com/2009/09/21/long-distance-vmotion/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WAN VMotion - A Step Closer to a Private Cloud? &#124; The SLOG - SimonLong/Blog</title>
		<link>http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/#comment-925</link>
		<dc:creator><![CDATA[WAN VMotion - A Step Closer to a Private Cloud? &#124; The SLOG - SimonLong/Blog]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 09:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/#comment-925</guid>
		<description><![CDATA[[...] from vinf.net recently commented on his blog post about this proof of concept, tells us; Before I had my GbE switch at home I could easily do [...]]]></description>
		<content:encoded><![CDATA[<p>[...] from vinf.net recently commented on his blog post about this proof of concept, tells us; Before I had my GbE switch at home I could easily do [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vinf</title>
		<link>http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/#comment-924</link>
		<dc:creator><![CDATA[vinf]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 08:36:03 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/#comment-924</guid>
		<description><![CDATA[I wonder if it will be latency or bandwidth that kills it? 

Before I had my GbE switch at home I could easily do vMotions between hosts over an old 100mb hub, 100mb WAN connections (at least within the UK) aren&#039;t beyond the realms of affordability for many organisations and 1Gb LES links also not too bad within the M25

The article doesn&#039;t make this clear but I assume it&#039;s still using a single piece of storage which is accessible from both DC&#039;s, if VMware could make long distance vMotion understand array mirroring (or via 3rd party storage virtualization like datacore etc.) then the actual bandwidth between the two DC&#039;s would be slightly less of a concern as ongoing execution will happen from DC-local storage and you rely on the array to ship the data to the secondary node&#039;s storage. this would need some kind of checkpoint/control mechanism which ESX controls - as long as you can sync the LUN/vmfs delta&#039;s between the two sites at the storage level with an acceptable latency for vMotion (and I&#039;ve made this work over a 100mb hub with ESX 3.5 before now)

This is similar to how EMC implemented long distance/stretched failover clusters with Exchange 2003/SQL - there was a plug-in product that handled the checkpointing of replication and reporting to the host.

Maybe not within the current release of the product, unless the new vSphere SATP/PSP modules can implement this? -  VMware - feature request? ;)]]></description>
		<content:encoded><![CDATA[<p>I wonder if it will be latency or bandwidth that kills it? </p>
<p>Before I had my GbE switch at home I could easily do vMotions between hosts over an old 100mb hub, 100mb WAN connections (at least within the UK) aren&#8217;t beyond the realms of affordability for many organisations and 1Gb LES links also not too bad within the M25</p>
<p>The article doesn&#8217;t make this clear but I assume it&#8217;s still using a single piece of storage which is accessible from both DC&#8217;s, if VMware could make long distance vMotion understand array mirroring (or via 3rd party storage virtualization like datacore etc.) then the actual bandwidth between the two DC&#8217;s would be slightly less of a concern as ongoing execution will happen from DC-local storage and you rely on the array to ship the data to the secondary node&#8217;s storage. this would need some kind of checkpoint/control mechanism which ESX controls &#8211; as long as you can sync the LUN/vmfs delta&#8217;s between the two sites at the storage level with an acceptable latency for vMotion (and I&#8217;ve made this work over a 100mb hub with ESX 3.5 before now)</p>
<p>This is similar to how EMC implemented long distance/stretched failover clusters with Exchange 2003/SQL &#8211; there was a plug-in product that handled the checkpointing of replication and reporting to the host.</p>
<p>Maybe not within the current release of the product, unless the new vSphere SATP/PSP modules can implement this? &#8211;  VMware &#8211; feature request? <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Long</title>
		<link>http://vinf.net/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/#comment-923</link>
		<dc:creator><![CDATA[Simon Long]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 08:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2009/06/30/long-distance-vmotion-heading-to-the-vcloud/#comment-923</guid>
		<description><![CDATA[Hi Simon, i have also just been reading this article. I think probably the biggest issue companies will have is available bandwith between DC&#039;s. 

I would be interested to see what the minimum bandwidth is needed to run a successful vMotion.

Simon]]></description>
		<content:encoded><![CDATA[<p>Hi Simon, i have also just been reading this article. I think probably the biggest issue companies will have is available bandwith between DC&#8217;s. </p>
<p>I would be interested to see what the minimum bandwidth is needed to run a successful vMotion.</p>
<p>Simon</p>
]]></content:encoded>
	</item>
</channel>
</rss>

