<?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: Hyper-V snapshots: not for production</title>
	<atom:link href="http://www.vcritical.com/2009/04/hyper-v-snapshots-not-for-production/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vcritical.com/2009/04/hyper-v-snapshots-not-for-production/</link>
	<description>Informed Virtualization Criticism</description>
	<lastBuildDate>Fri, 30 Jul 2010 12:54:25 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Be carefull with shapshots in Hyper-V &#171; UP2V</title>
		<link>http://www.vcritical.com/2009/04/hyper-v-snapshots-not-for-production/#comment-6698</link>
		<dc:creator>Be carefull with shapshots in Hyper-V &#171; UP2V</dc:creator>
		<pubDate>Fri, 22 May 2009 11:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1009#comment-6698</guid>
		<description>[...] Gray of vCritical.com has an opinion about this [...]</description>
		<content:encoded><![CDATA[<p>[...] Gray of vCritical.com has an opinion about this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/04/hyper-v-snapshots-not-for-production/#comment-6029</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Sat, 25 Apr 2009 02:40:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1009#comment-6029</guid>
		<description>Etienne, great point about XenServer, I&#039;m sure that comes as a surprise to many people.  VMware ESX snapshots are storage-independent.</description>
		<content:encoded><![CDATA[<p>Etienne, great point about XenServer, I&#8217;m sure that comes as a surprise to many people.  VMware ESX snapshots are storage-independent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Etienne Pouliot</title>
		<link>http://www.vcritical.com/2009/04/hyper-v-snapshots-not-for-production/#comment-6026</link>
		<dc:creator>Etienne Pouliot</dc:creator>
		<pubDate>Sat, 25 Apr 2009 01:53:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1009#comment-6026</guid>
		<description>I totally agree with you.  Furthermore, that&#039;s exactly the same reason I do not recommend Xenserver.  You don&#039;t get snapshots with Xenserver unless you are connected to a Dell or a NetApp SAN (Details in blog (in french)).  In my mind, VMware is the only &quot;production ready&quot;  virtualization product.</description>
		<content:encoded><![CDATA[<p>I totally agree with you.  Furthermore, that&#8217;s exactly the same reason I do not recommend Xenserver.  You don&#8217;t get snapshots with Xenserver unless you are connected to a Dell or a NetApp SAN (Details in blog (in french)).  In my mind, VMware is the only &#8220;production ready&#8221;  virtualization product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/04/hyper-v-snapshots-not-for-production/#comment-6025</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Fri, 24 Apr 2009 19:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1009#comment-6025</guid>
		<description>Shawn, thanks for the comment.  Yes, it is as you describe -- the existing snapshot file just keeps growing until you power the VM off.  When Microsoft says not recommended for production, they are not kidding!

I&#039;m glad you find the VCritical articles useful, good idea to write up a summary page on the topic.  I&#039;ll consider it.</description>
		<content:encoded><![CDATA[<p>Shawn, thanks for the comment.  Yes, it is as you describe &#8212; the existing snapshot file just keeps growing until you power the VM off.  When Microsoft says not recommended for production, they are not kidding!</p>
<p>I&#8217;m glad you find the VCritical articles useful, good idea to write up a summary page on the topic.  I&#8217;ll consider it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://www.vcritical.com/2009/04/hyper-v-snapshots-not-for-production/#comment-6024</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Fri, 24 Apr 2009 19:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1009#comment-6024</guid>
		<description>If you create a Hyper-V snapshot, a snapshot file is created and grows as changes are made to the VM. If I then decide to delete that snapshot, (merge not revert) the changes are not merged until the VM is powered off.
Thats easy to understand, but where are the writes happening between the time I &#039;delete&#039; the snapshot and the VM being powered off and the merge happens. Do they continue against the snapshot file, causing it to continue to still grow? That is just retarded if that is the case. What if the reason I &#039;deleted&#039; the snaphot was because of space constraints? Will I have to suffer downtime to poweroff the VM because of this?

On another note - I would do this but I&#039;m lazy :) 
You should compile a list with brief description and links, for each of these little issues with Hyper-V and SCVMM youve blogged about over the past months. This allow those of us in pre-sales roles to give customers looking at a Hyper-V solution complete facts about what they may be getting themselves into. Not everything is in the feature/price comparison, day to day operational issue matter as well.</description>
		<content:encoded><![CDATA[<p>If you create a Hyper-V snapshot, a snapshot file is created and grows as changes are made to the VM. If I then decide to delete that snapshot, (merge not revert) the changes are not merged until the VM is powered off.<br />
Thats easy to understand, but where are the writes happening between the time I &#8216;delete&#8217; the snapshot and the VM being powered off and the merge happens. Do they continue against the snapshot file, causing it to continue to still grow? That is just retarded if that is the case. What if the reason I &#8216;deleted&#8217; the snaphot was because of space constraints? Will I have to suffer downtime to poweroff the VM because of this?</p>
<p>On another note &#8211; I would do this but I&#8217;m lazy <img src='http://www.vcritical.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
You should compile a list with brief description and links, for each of these little issues with Hyper-V and SCVMM youve blogged about over the past months. This allow those of us in pre-sales roles to give customers looking at a Hyper-V solution complete facts about what they may be getting themselves into. Not everything is in the feature/price comparison, day to day operational issue matter as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
