<?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: Easy recovery from a full VMware ESX datastore</title>
	<atom:link href="http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/</link>
	<description>Informed Virtualization Criticism</description>
	<lastBuildDate>Thu, 09 Feb 2012 04:50:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Amal</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-11451</link>
		<dc:creator>Amal</dc:creator>
		<pubDate>Sun, 23 Jan 2011 05:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-11451</guid>
		<description>I&#039;ve not tried this in 4.1 but does ESX perform the same pause function if the datastore goes offline completely? If not, it should. A couple years ago I had a catastrophic loss of service with one of my iSCSI storage arrays. Recovery was simple, but the VM guests had all hard-crashed. It would be nice if those machines could have been put into instantaneous suspension (halt and suspend all CPU and storage calls) until the storage array was able to be brought back online.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve not tried this in 4.1 but does ESX perform the same pause function if the datastore goes offline completely? If not, it should. A couple years ago I had a catastrophic loss of service with one of my iSCSI storage arrays. Recovery was simple, but the VM guests had all hard-crashed. It would be nice if those machines could have been put into instantaneous suspension (halt and suspend all CPU and storage calls) until the storage array was able to be brought back online.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Objective 6.4 : Troubleshoot Storage Performance and Connectivity</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-11105</link>
		<dc:creator>Objective 6.4 : Troubleshoot Storage Performance and Connectivity</dc:creator>
		<pubDate>Thu, 19 Aug 2010 10:17:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-11105</guid>
		<description>[...] http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/" rel="nofollow">http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-8217</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Fri, 09 Oct 2009 14:22:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-8217</guid>
		<description>That is good to know, thanks for the details.  So all of the VMs on a LUN get paused at the same time whether or not they need additional storage -- then it is a race against the 200MB clock.  For the VMs that don&#039;t make it... unpredictable results.

Monitoring virtualization storage is crucial, which is why vSphere accounts not only for space currently used but for space allocated by thin provisioning -- critical for managing risk.  As far as I can tell, SCOM doesn&#039;t address this aspect.</description>
		<content:encoded><![CDATA[<p>That is good to know, thanks for the details.  So all of the VMs on a LUN get paused at the same time whether or not they need additional storage &#8212; then it is a race against the 200MB clock.  For the VMs that don&#8217;t make it&#8230; unpredictable results.</p>
<p>Monitoring virtualization storage is crucial, which is why vSphere accounts not only for space currently used but for space allocated by thin provisioning &#8212; critical for managing risk.  As far as I can tell, SCOM doesn&#8217;t address this aspect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stu Fox</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-8213</link>
		<dc:creator>Stu Fox</dc:creator>
		<pubDate>Fri, 09 Oct 2009 00:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-8213</guid>
		<description>You&#039;ll get warned in the event log at 2GB free, and at 200MB free the VM&#039;s will get paused on Hyper-V.  That would be the worst case - that you ignored the warnings and didn&#039;t take action.  Of course with OpsMgr you would get warned earlier.</description>
		<content:encoded><![CDATA[<p>You&#8217;ll get warned in the event log at 2GB free, and at 200MB free the VM&#8217;s will get paused on Hyper-V.  That would be the worst case &#8211; that you ignored the warnings and didn&#8217;t take action.  Of course with OpsMgr you would get warned earlier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-8209</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Thu, 08 Oct 2009 20:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-8209</guid>
		<description>Stu,

That would not be the &lt;em&gt;worst case&lt;/em&gt; -- more like &lt;em&gt; best case&lt;/em&gt;.  If it ever happens to you, let me know.

Eric</description>
		<content:encoded><![CDATA[<p>Stu,</p>
<p>That would not be the <em>worst case</em> &#8212; more like <em> best case</em>.  If it ever happens to you, let me know.</p>
<p>Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stu Fox</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-8201</link>
		<dc:creator>Stu Fox</dc:creator>
		<pubDate>Thu, 08 Oct 2009 00:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-8201</guid>
		<description>By not pretty you mean worst case when the machines get paused just like on VMware?  

Of course you&#039;d be monitoring the host volume with OpsMgr so it would proactively alert you anyway and you&#039;d have planned for that.  Hell, even perfmon would probably do that for you.</description>
		<content:encoded><![CDATA[<p>By not pretty you mean worst case when the machines get paused just like on VMware?  </p>
<p>Of course you&#8217;d be monitoring the host volume with OpsMgr so it would proactively alert you anyway and you&#8217;d have planned for that.  Hell, even perfmon would probably do that for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-8198</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Wed, 07 Oct 2009 17:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-8198</guid>
		<description>Jason, thanks for pointing out those additional recovery choices.

Ben, interesting idea.  If you come up with something let me know.  Nice blog, by the way.</description>
		<content:encoded><![CDATA[<p>Jason, thanks for pointing out those additional recovery choices.</p>
<p>Ben, interesting idea.  If you come up with something let me know.  Nice blog, by the way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Thomas</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-8188</link>
		<dc:creator>Ben Thomas</dc:creator>
		<pubDate>Wed, 07 Oct 2009 00:44:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-8188</guid>
		<description>Cool post!  I would be interested to try that with some preventative alarms to automatically move off powered off VMs with powerCLI.  Seems to make a case for an &quot;emergency&quot; empty LUN for situations like this.</description>
		<content:encoded><![CDATA[<p>Cool post!  I would be interested to try that with some preventative alarms to automatically move off powered off VMs with powerCLI.  Seems to make a case for an &#8220;emergency&#8221; empty LUN for situations like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Boche</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-8187</link>
		<dc:creator>Jason Boche</dc:creator>
		<pubDate>Tue, 06 Oct 2009 23:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-8187</guid>
		<description>Another option for the back pocket:  Find a VM that can be powered off.  Chances are (and by default) it has no memory reservation configured.  The net result is that when the VM is powered off, a VMkernel swap file equal to the size of assigned RAM can safely be removed when the VM is powered down.  

Alternatively, creating a reservation equal to assigned memory on the fly will zero out the swap file but the zeroing won&#039;t actually happen until the next power operation of the VM.</description>
		<content:encoded><![CDATA[<p>Another option for the back pocket:  Find a VM that can be powered off.  Chances are (and by default) it has no memory reservation configured.  The net result is that when the VM is powered off, a VMkernel swap file equal to the size of assigned RAM can safely be removed when the VM is powered down.  </p>
<p>Alternatively, creating a reservation equal to assigned memory on the fly will zero out the swap file but the zeroing won&#8217;t actually happen until the next power operation of the VM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention How to recover when a VMware ESX datastore runs out of space &#124; VCritical -- Topsy.com</title>
		<link>http://www.vcritical.com/2009/10/easy-recovery-from-a-full-vmware-esx-datastore/#comment-8186</link>
		<dc:creator>Tweets that mention How to recover when a VMware ESX datastore runs out of space &#124; VCritical -- Topsy.com</dc:creator>
		<pubDate>Tue, 06 Oct 2009 22:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1757#comment-8186</guid>
		<description>[...] This post was mentioned on Twitter by VMware Planet V12n. VMware Planet V12n said: Easy recovery from a full VMware ESX datastore (VCritical) http://bit.ly/DXVGX [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by VMware Planet V12n. VMware Planet V12n said: Easy recovery from a full VMware ESX datastore (VCritical) <a href="http://bit.ly/DXVGX" rel="nofollow">http://bit.ly/DXVGX</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

