<?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: How to quickly recover from disaster</title>
	<atom:link href="http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/</link>
	<description>Your P.I. on virtualization</description>
	<lastBuildDate>Tue, 07 Feb 2012 11:19:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Internetforumuser</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-1706</link>
		<dc:creator>Internetforumuser</dc:creator>
		<pubDate>Thu, 15 Dec 2011 06:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-1706</guid>
		<description>Sanjai,

I am not sure if you will read this because your post is over a year hold; however, I want to give it a try. In your case of the Multiple PSOD&#039;s, do you know what was on the PSOD itself? I recently experienced an issue with multiple PSODS at the same time on the same cluster. This cluster had been fully functional for over a year and we have never had any issues. Our Cluster has both CLARiiON and HDS LUNS; therefore, our systems seem similar.

Let me know if you have as screen capture of your PSOD..

Please email internetforumuser@gmail.com
@gmail:disqus 
Thanks</description>
		<content:encoded><![CDATA[<p>Sanjai,</p>
<p>I am not sure if you will read this because your post is over a year hold; however, I want to give it a try. In your case of the Multiple PSOD&#8217;s, do you know what was on the PSOD itself? I recently experienced an issue with multiple PSODS at the same time on the same cluster. This cluster had been fully functional for over a year and we have never had any issues. Our Cluster has both CLARiiON and HDS LUNS; therefore, our systems seem similar.</p>
<p>Let me know if you have as screen capture of your PSOD..</p>
<p>Please email <a href="mailto:internetforumuser@gmail.com">internetforumuser@gmail.com</a><br />
@gmail:disqus <br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jasondinsdale</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-904</link>
		<dc:creator>jasondinsdale</dc:creator>
		<pubDate>Tue, 18 May 2010 02:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-904</guid>
		<description>Gabe - did you ever write that PowerShell?  Here&#039;s one a wrote a little while back which allows you to run VC / SQL / DCs on any host through DRS as it goes and finds the VMs for you and powers on in the right sequence.  It&#039;s one of my first scripts so be gentle!  BTW - like your idea of a priority field to sequence the startup of other VMs ... will look at extending my script based on that idea.&lt;br&gt;&lt;br&gt;# ====================================================================&lt;br&gt;# ColdStart.ps1 - Restart key infrastructure components.&lt;br&gt;# Sequence:&lt;br&gt;# 1 - Find and start DCs.&lt;br&gt;# 2 - Find and start SQL Server (if necessary).&lt;br&gt;# 3 - Find and start VC.&lt;br&gt;#&lt;br&gt;# Rev 1.0 - Initial release&lt;br&gt;# ====================================================================&lt;br&gt;&lt;br&gt;function start_VM {&lt;br&gt;	param ($VMs)&lt;br&gt;	foreach ($Esx in $EsxCreds.keys) {&lt;br&gt;		Connect-VIServer -Server $Esx -User &quot;root&quot; -Password $EsxCreds.$Esx -wa silentlycontinue &#124; Out-Null  &lt;br&gt;		$Found = Get-VM $VMs -ea silentlycontinue -wa silentlycontinue&lt;br&gt;        if ( $Found ) {&lt;br&gt;               foreach ($FoundVM in $Found) {&lt;br&gt;                   if ( $FoundVM.PowerState -ne &quot;PoweredOn&quot; ) {&lt;br&gt;                        Write-Host &quot;    Found powered off VM &#039;$FoundVM&#039; on ESX host $Esx&quot;&lt;br&gt;                        Write-Host &quot;    POWERING ON...&quot;&lt;br&gt;                        Start-VM $FoundVM&lt;br&gt;                    } else {&lt;br&gt;                        Write-Host &quot;    Found already powered on VM &#039;$FoundVM&#039; on ESX host $Esx&quot;&lt;br&gt;                    }&lt;br&gt;               }&lt;br&gt;        }&lt;br&gt;		Disconnect-VIServer * -Confirm:$false &lt;br&gt;	}&lt;br&gt;}&lt;br&gt;&lt;br&gt;# Setup&lt;br&gt;&lt;br&gt;if ( ! (Get-PSSnapin VMware.VimAutomation.Core) ) { Add-PSSnapin VMware.VimAutomation.Core &#124; Out-Null }&lt;br&gt;&lt;br&gt;# Define the ESX hostname/IP &amp; credential pairs here....&lt;br&gt;&lt;br&gt;$EsxCreds = @{&lt;br&gt;    &quot;x.x.x.1&quot; = &#039;rootpassword1&#039;;&lt;br&gt;    &quot;x.x.x.2&quot; = &#039;rootpassword2&#039; }&lt;br&gt;&lt;br&gt;# Specify the names of the VMs that are DCs (leave blank if none). &lt;br&gt;$DCs = (&quot;DC1&quot;,&quot;DC2&quot;)&lt;br&gt;&lt;br&gt;# Specify the name of the SQL Server VM that that supports VC (leave blank if SQL is local to VC). &lt;br&gt;$SQL = &quot;SQL&quot;&lt;br&gt;&lt;br&gt;# Specify the name of the VC VM. &lt;br&gt;$VC  = &quot;VC&quot;&lt;br&gt;&lt;br&gt;# Fire &#039;em up.&lt;br&gt;&lt;br&gt;Write-Host &quot;ColdStart.ps1 STARTING&quot;&lt;br&gt;Write-Host &quot;&quot;&lt;br&gt;&lt;br&gt;if ( $DCs ) {&lt;br&gt;    Write-Host &quot;STATUS: Looking for Domain Controller VMs ...&quot;&lt;br&gt;    start_VM $DCs&lt;br&gt;}&lt;br&gt;&lt;br&gt;if ( $SQL ) {&lt;br&gt;    Write-Host &quot;STATUS: Looking for SQL Server VM (which supports VC) ...&quot;&lt;br&gt;    start_VM $SQL&lt;br&gt;}&lt;br&gt;&lt;br&gt;Write-Host &quot;STATUS: Looking for vCenter Server VM ...&quot;&lt;br&gt;Write-Host &quot;&quot;&lt;br&gt;&lt;br&gt;start_VM $VC&lt;br&gt;&lt;br&gt;Write-Host &quot;&quot;&lt;br&gt;Write-Host &quot;ColdStart.ps1 COMPLETE&quot;</description>
		<content:encoded><![CDATA[<p>Gabe &#8211; did you ever write that PowerShell?  Here&#39;s one a wrote a little while back which allows you to run VC / SQL / DCs on any host through DRS as it goes and finds the VMs for you and powers on in the right sequence.  It&#39;s one of my first scripts so be gentle!  BTW &#8211; like your idea of a priority field to sequence the startup of other VMs &#8230; will look at extending my script based on that idea.</p>
<p># ====================================================================<br /># ColdStart.ps1 &#8211; Restart key infrastructure components.<br /># Sequence:<br /># 1 &#8211; Find and start DCs.<br /># 2 &#8211; Find and start SQL Server (if necessary).<br /># 3 &#8211; Find and start VC.<br />#<br /># Rev 1.0 &#8211; Initial release<br /># ====================================================================</p>
<p>function start_VM {<br />	param ($VMs)<br />	foreach ($Esx in $EsxCreds.keys) {<br />		Connect-VIServer -Server $Esx -User &#8220;root&#8221; -Password $EsxCreds.$Esx -wa silentlycontinue | Out-Null  <br />		$Found = Get-VM $VMs -ea silentlycontinue -wa silentlycontinue<br />        if ( $Found ) {<br />               foreach ($FoundVM in $Found) {<br />                   if ( $FoundVM.PowerState -ne &#8220;PoweredOn&#8221; ) {<br />                        Write-Host &#8221;    Found powered off VM &#39;$FoundVM&#39; on ESX host $Esx&#8221;<br />                        Write-Host &#8221;    POWERING ON&#8230;&#8221;<br />                        Start-VM $FoundVM<br />                    } else {<br />                        Write-Host &#8221;    Found already powered on VM &#39;$FoundVM&#39; on ESX host $Esx&#8221;<br />                    }<br />               }<br />        }<br />		Disconnect-VIServer * -Confirm:$false <br />	}<br />}</p>
<p># Setup</p>
<p>if ( ! (Get-PSSnapin VMware.VimAutomation.Core) ) { Add-PSSnapin VMware.VimAutomation.Core | Out-Null }</p>
<p># Define the ESX hostname/IP &#038; credential pairs here&#8230;.</p>
<p>$EsxCreds = @{<br />    &#8220;x.x.x.1&#8243; = &#39;rootpassword1&#39;;<br />    &#8220;x.x.x.2&#8243; = &#39;rootpassword2&#39; }</p>
<p># Specify the names of the VMs that are DCs (leave blank if none). <br />$DCs = (&#8220;DC1&#8243;,&#8221;DC2&#8243;)</p>
<p># Specify the name of the SQL Server VM that that supports VC (leave blank if SQL is local to VC). <br />$SQL = &#8220;SQL&#8221;</p>
<p># Specify the name of the VC VM. <br />$VC  = &#8220;VC&#8221;</p>
<p># Fire &#39;em up.</p>
<p>Write-Host &#8220;ColdStart.ps1 STARTING&#8221;<br />Write-Host &#8220;&#8221;</p>
<p>if ( $DCs ) {<br />    Write-Host &#8220;STATUS: Looking for Domain Controller VMs &#8230;&#8221;<br />    start_VM $DCs<br />}</p>
<p>if ( $SQL ) {<br />    Write-Host &#8220;STATUS: Looking for SQL Server VM (which supports VC) &#8230;&#8221;<br />    start_VM $SQL<br />}</p>
<p>Write-Host &#8220;STATUS: Looking for vCenter Server VM &#8230;&#8221;<br />Write-Host &#8220;&#8221;</p>
<p>start_VM $VC</p>
<p>Write-Host &#8220;&#8221;<br />Write-Host &#8220;ColdStart.ps1 COMPLETE&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabes Virtual World&#187; VMware vSphere 4 default installation settings &#8211; Gabe&#8217;s Virtual World</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-901</link>
		<dc:creator>Gabes Virtual World&#187; VMware vSphere 4 default installation settings &#8211; Gabe&#8217;s Virtual World</dc:creator>
		<pubDate>Thu, 13 May 2010 11:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-901</guid>
		<description>[...] Virtual Machine Options -&gt; Exclude the vCenter server and the connected SQL Server from DRS. Set to â€œdisabledâ€. Always place vCenter on the first ESX host in the cluster. When first host has to be set to maintenance mode, move to second host. For SQL server, place it on the second host and move to first host when in maintenance mode. Also see: http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Virtual Machine Options -&gt; Exclude the vCenter server and the connected SQL Server from DRS. Set to â€œdisabledâ€. Always place vCenter on the first ESX host in the cluster. When first host has to be set to maintenance mode, move to second host. For SQL server, place it on the second host and move to first host when in maintenance mode. Also see: <a href="http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/" rel="nofollow">http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabrie van Zanten</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-723</link>
		<dc:creator>Gabrie van Zanten</dc:creator>
		<pubDate>Tue, 01 Dec 2009 19:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-723</guid>
		<description>Root cause was because storage connection to secondary site got disconnected for a short time and the SAN responded to ESX with a reply ESX didn&#039;t understand and therefore threw an exception.&lt;br&gt;&lt;br&gt;As the VMware engineer explained, when ESX gets a response it doesn&#039;t know how to handle, it can&#039;t just do anything with it. The only proper action is to exit the building.</description>
		<content:encoded><![CDATA[<p>Root cause was because storage connection to secondary site got disconnected for a short time and the SAN responded to ESX with a reply ESX didn&#39;t understand and therefore threw an exception.</p>
<p>As the VMware engineer explained, when ESX gets a response it doesn&#39;t know how to handle, it can&#39;t just do anything with it. The only proper action is to exit the building.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PiroNet</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-722</link>
		<dc:creator>PiroNet</dc:creator>
		<pubDate>Tue, 01 Dec 2009 19:00:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-722</guid>
		<description>up on the root cause!?</description>
		<content:encoded><![CDATA[<p>up on the root cause!?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabrie van Zanten</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-489</link>
		<dc:creator>Gabrie van Zanten</dc:creator>
		<pubDate>Tue, 01 Dec 2009 12:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-489</guid>
		<description>Root cause was because storage connection to secondary site got disconnected for a short time and the SAN responded to ESX with a reply ESX didn&#039;t understand and therefore threw an exception.&lt;br&gt;&lt;br&gt;As the VMware engineer explained, when ESX gets a response it doesn&#039;t know how to handle, it can&#039;t just do anything with it. The only proper action is to exit the building.</description>
		<content:encoded><![CDATA[<p>Root cause was because storage connection to secondary site got disconnected for a short time and the SAN responded to ESX with a reply ESX didn&#39;t understand and therefore threw an exception.</p>
<p>As the VMware engineer explained, when ESX gets a response it doesn&#39;t know how to handle, it can&#39;t just do anything with it. The only proper action is to exit the building.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PiroNet</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-488</link>
		<dc:creator>PiroNet</dc:creator>
		<pubDate>Tue, 01 Dec 2009 12:00:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-488</guid>
		<description>up on the root cause!?</description>
		<content:encoded><![CDATA[<p>up on the root cause!?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: About ESXi lockdown mode &#124; Nexus Technologies - IT Company providing Virtualisation Solutions, IT managed Services and IT Consultancy</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-487</link>
		<dc:creator>About ESXi lockdown mode &#124; Nexus Technologies - IT Company providing Virtualisation Solutions, IT managed Services and IT Consultancy</dc:creator>
		<pubDate>Mon, 30 Nov 2009 21:15:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-487</guid>
		<description>[...] virtual infrastructure has been down, is to get vCenter up and running again. In a previous post â€œHow to quickly recover from disasterâ€ I already explained the idea of running vCenter always on the first host in your cluster. In [...]</description>
		<content:encoded><![CDATA[<p>[...] virtual infrastructure has been down, is to get vCenter up and running again. In a previous post â€œHow to quickly recover from disasterâ€ I already explained the idea of running vCenter always on the first host in your cluster. In [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Beaver</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-202</link>
		<dc:creator>Steve Beaver</dc:creator>
		<pubDate>Fri, 02 Jan 2009 16:57:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-202</guid>
		<description>Hey Gabe,
You can not just leave it like that.  Inquiring minds want to know what really happened so we can learn from this.

Steve</description>
		<content:encoded><![CDATA[<p>Hey Gabe,<br />
You can not just leave it like that.  Inquiring minds want to know what really happened so we can learn from this.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SimonLong</title>
		<link>http://www.gabesvirtualworld.com/how-to-quickly-recover-from-disaster/#comment-199</link>
		<dc:creator>SimonLong</dc:creator>
		<pubDate>Wed, 24 Dec 2008 11:48:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=114#comment-199</guid>
		<description>Gabe, great read. I will certiainly be taking some tips from your situation and implementing them before im ever faced with a PSOD.

Simon</description>
		<content:encoded><![CDATA[<p>Gabe, great read. I will certiainly be taking some tips from your situation and implementing them before im ever faced with a PSOD.</p>
<p>Simon</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.gabesvirtualworld.com @ 2012-02-09 09:32:18 -->
