<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WJPatton.com</title>
	<atom:link href="http://wjpatton.com/index.php/feed/" rel="self" type="application/rss+xml" />
	<link>http://wjpatton.com</link>
	<description></description>
	<lastBuildDate>Tue, 09 Mar 2010 18:10:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Interpreting ESXTOP files with ESXPlot</title>
		<link>http://wjpatton.com/index.php/2010/02/interpreting-esxtop-files-with-esxplot/</link>
		<comments>http://wjpatton.com/index.php/2010/02/interpreting-esxtop-files-with-esxplot/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 04:14:32 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[drummonds]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[esxplot]]></category>
		<category><![CDATA[esxtop]]></category>
		<category><![CDATA[perfmon]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[vpivot]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=234</guid>
		<description><![CDATA[Scott Drummonds of vPivot.com posted on ESXPlot, a great tool that is far more efficient and less aggravating than Perfmon for working with ESXTOP output files.
Geoff White has created a badly needed tool here, Perfmon worked but was very time consuming.  Especially with those days or weeks of ESXTOP statistic files.
Extract and use the README.  For Windows, extract all [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://twitter.com/drummonds" target="_blank">Scott Drummonds</a> of <a href="http://vpivot.com" target="_blank">vPivot.com</a> posted on <a href="http://vpivot.com/2010/01/13/esxplot-1-0-released/" target="_blank">ESXPlot</a>, a great tool that is far more efficient and less aggravating than Perfmon for working with ESXTOP output files.</p>
<p>Geoff White has created a badly needed tool here, Perfmon worked but was very time consuming.  Especially with those days or weeks of ESXTOP statistic files.</p>
<p>Extract and use the README.  For Windows, extract all files, navigate to the esxplot.exe in the Bin directory and you are off and running!</p>
<p>Geoff White now has a full project site with all information and releases.  <a href="http://www.durganetworks.com/esxplot" target="_blank">Click here</a></p>
<p>Labs.vmware.com has now gone live and hosting ESXPlot as well.  <a href="http://labs.vmware.com/flings/esxplot" target="_blank">Click here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/02/interpreting-esxtop-files-with-esxplot/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>VMware Clustering vCenter Server 4 on MSCS</title>
		<link>http://wjpatton.com/index.php/2010/01/vmware-clustering-vcenter-server-4-on-mscs/</link>
		<comments>http://wjpatton.com/index.php/2010/01/vmware-clustering-vcenter-server-4-on-mscs/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 23:21:23 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[MSCS]]></category>
		<category><![CDATA[vcenter]]></category>
		<category><![CDATA[viops]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=229</guid>
		<description><![CDATA[VIOPS has a good document on how to cluster the vCenter services on MSCS.  Things have changed slightly from 2.5 and though most of the steps will be old news for some, there are a couple changes so be sure to review before proceeding with your Install/Upgrade projects.  It does have a nice section on [...]]]></description>
			<content:encoded><![CDATA[<p>VIOPS has a good document on how to cluster the vCenter services on MSCS.  Things have changed slightly from 2.5 and though most of the steps will be old news for some, there are a couple changes so be sure to review before proceeding with your Install/Upgrade projects.  It does have a nice section on upgrading existing clusters as well.</p>
<p><a href="http://communities.vmware.com/docs/DOC-11538;jsessionid=FB143DF579731618946B0565CFB5B94F" target="_blank">Get the document here.</a></p>
<p>One special note I would point out is running the &#8220;jointool.bat&#8221; for replicating roles at the end of your cluster config.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/01/vmware-clustering-vcenter-server-4-on-mscs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1003797 &#8211; Unable to migrate: Virtual machine is configured to use a device that prevents migration</title>
		<link>http://wjpatton.com/index.php/2010/01/vmware-kb1003797-unable-to-migrate-virtual-machine-is-configured-to-use-a-device-that-prevents-migration/</link>
		<comments>http://wjpatton.com/index.php/2010/01/vmware-kb1003797-unable-to-migrate-virtual-machine-is-configured-to-use-a-device-that-prevents-migration/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 19:13:26 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[KB]]></category>
		<category><![CDATA[MSCS]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=227</guid>
		<description><![CDATA[There seems to be a lot of confusion about vMotion and bus-shared VMDKs.  For the record, and from VMware, it is not recommended nor supported to vMotion your VM between ESX Hosts when using either Virtual or Physical mode bus-sharing.
Please see the KB here.
I know there are plenty that will disagree and have found ways [...]]]></description>
			<content:encoded><![CDATA[<p>There seems to be a lot of confusion about vMotion and bus-shared VMDKs.  For the record, and from VMware, it is not recommended nor supported to vMotion your VM between ESX Hosts when using either Virtual or Physical mode bus-sharing.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003797" target="_blank">Please see the KB here.</a></p>
<p>I know there are plenty that will disagree and have found ways of doing it, but within our environments for our MSCS clusters using Physical mode, we disable DRS and only Cold vMotion once the resources of the cluster have been moved off the Node and the VM is Powered Off.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/01/vmware-kb1003797-unable-to-migrate-virtual-machine-is-configured-to-use-a-device-that-prevents-migration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware vSphere Hardening Guide &#8211; Draft Rev. B</title>
		<link>http://wjpatton.com/index.php/2010/01/vmware-vsphere-hardening-guide-draft-rev-b/</link>
		<comments>http://wjpatton.com/index.php/2010/01/vmware-vsphere-hardening-guide-draft-rev-b/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 15:46:54 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[hardening]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=223</guid>
		<description><![CDATA[VMware has released a draft of the vSphere Hardening Guide, and are encouraging feedback from the community.  It is broken into multiple pieces.
Part 1: Introduction
Part 2: Virtual Machines
Part 3: Host
Part 4: vNetwork
Part 5: vCenter
Part 6: COS
]]></description>
			<content:encoded><![CDATA[<p>VMware has released a draft of the vSphere Hardening Guide, and are encouraging feedback from the community.  It is broken into multiple pieces.</p>
<p>Part 1: <a href="http://communities.vmware.com/docs/DOC-11843;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">Introduction</a></p>
<p>Part 2: <a href="http://communities.vmware.com/docs/DOC-11844;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">Virtual Machines</a></p>
<p>Part 3: <a href="http://communities.vmware.com/docs/DOC-11845;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">Host</a></p>
<p>Part 4: <a href="http://communities.vmware.com/docs/DOC-11846;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">vNetwork</a></p>
<p>Part 5: <a href="http://communities.vmware.com/docs/DOC-11847;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">vCenter</a></p>
<p>Part 6: <a href="http://communities.vmware.com/docs/DOC-11848;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">COS</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/01/vmware-vsphere-hardening-guide-draft-rev-b/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1011170 &#8211; Checking Zero vs EagerZero Disk Status</title>
		<link>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/</link>
		<comments>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 18:43:59 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[esxi4]]></category>
		<category><![CDATA[KB]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=220</guid>
		<description><![CDATA[VMware has released a KB with a handy vmfstools command to check your VM&#8217;s disk status.  If the VMFS output shows a &#8220;Z&#8221; it is Zerothick with blocks that have not been written to yet.
Read the article here.
This allows you to check the disk status for options such as Fault Tolerance or Microsoft Cluster Services.  [...]]]></description>
			<content:encoded><![CDATA[<p>VMware has released a KB with a handy vmfstools command to check your VM&#8217;s disk status.  If the VMFS output shows a &#8220;Z&#8221; it is Zerothick with blocks that have not been written to yet.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1011170" target="_blank">Read the article here.</a></p>
<p>This allows you to check the disk status for options such as Fault Tolerance or Microsoft Cluster Services.  The disks must be in an Eagerzerothick format for these options to work.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scott Lowe moving to EMC</title>
		<link>http://wjpatton.com/index.php/2009/12/scott-lowe-moving-to-emc/</link>
		<comments>http://wjpatton.com/index.php/2009/12/scott-lowe-moving-to-emc/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 18:11:24 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[emc]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=214</guid>
		<description><![CDATA[Even during an economic slowdown there are bright spots and opportunities.  Scott Lowe from Blog.ScottLowe.org is taking a new position with EMC as a VMware-Cisco Solutions Principal.  Congratulations to Scott!
Scott has pledged to continue his already top-notch blogging, continuing in line with his new boss and another great blogger Chad Sakac.
Read Scott&#8217;s post on his [...]]]></description>
			<content:encoded><![CDATA[<p>Even during an economic slowdown there are bright spots and opportunities.  <a href="http://twitter.com/scott_lowe" target="_blank">Scott Lowe</a> from <a href="http://blog.scottlowe.org" target="_blank">Blog.ScottLowe.org</a> is taking a new position with EMC as a VMware-Cisco Solutions Principal.  Congratulations to Scott!</p>
<p>Scott has pledged to continue his already top-notch blogging, continuing in line with his new boss and another great blogger <a href="http://twitter.com/sakacc" target="_blank">Chad Sakac</a>.</p>
<p>Read Scott&#8217;s post on his site.  <a href="http://blog.scottlowe.org/2009/12/28/so-long-status-quo/" target="_blank">Read More</a></p>
<p>Thank you Scott for everything you have contributed and this opportunity, you deserve it.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/12/scott-lowe-moving-to-emc/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>VMware KB1016262 &#8211; vCenter Agent Install Fails on ESXi 4 Host</title>
		<link>http://wjpatton.com/index.php/2009/12/vmware-kb1016262-vcenter-agent-install-fails-on-esxi-4-host/</link>
		<comments>http://wjpatton.com/index.php/2009/12/vmware-kb1016262-vcenter-agent-install-fails-on-esxi-4-host/#comments</comments>
		<pubDate>Thu, 10 Dec 2009 16:52:34 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[agent]]></category>
		<category><![CDATA[esxi4]]></category>
		<category><![CDATA[KB]]></category>
		<category><![CDATA[vcenter]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=211</guid>
		<description><![CDATA[VMware just posted an alert on this for ESXi 4 Hosts managed by either vCenter 4 or 4 Update 1.  If you remove and re-add the Host to vCenter, or upgrade vCenter to Update 1 you may experience this issue.
At this time, there is no official fix, however it appears a reboot should fix the [...]]]></description>
			<content:encoded><![CDATA[<p>VMware just posted an alert on this for ESXi 4 Hosts managed by either vCenter 4 or 4 Update 1.  If you remove and re-add the Host to vCenter, or upgrade vCenter to Update 1 you may experience this issue.</p>
<p>At this time, there is no official fix, however it appears a reboot should fix the issue but with the Host disconnected from vCenter; vMotion is not an option and the disconnect may trigger HA, but I would hope that you have placed this host into Maintenance Mode prior to disconnecting from vCenter&#8230;right?  Also, HA should have been disabled prior to your Update 1 patch&#8230;you did that as well, right?</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1016262" target="_blank">Read the official VMware Alert here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/12/vmware-kb1016262-vcenter-agent-install-fails-on-esxi-4-host/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Symantec Doc. ID &#8211; 330033 &#8211; MSSQL Netbackup DB Backup Skipped</title>
		<link>http://wjpatton.com/index.php/2009/11/symantec-doc-id-330033-mssql-netbackup-db-backup-skipped/</link>
		<comments>http://wjpatton.com/index.php/2009/11/symantec-doc-id-330033-mssql-netbackup-db-backup-skipped/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 20:33:30 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Symantec]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[netbackup]]></category>
		<category><![CDATA[sql]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=208</guid>
		<description><![CDATA[There is an issue with all versions of Netbackup 6.5 through the latest 6.5.5.  This issue might cause the backup of a large number of databases to become unreliable and skip databases.
Read the full Document here.
We have seen this behavior on a few systems, and found that carving up the backups into smaller batch files [...]]]></description>
			<content:encoded><![CDATA[<p>There is an issue with all versions of Netbackup 6.5 through the latest 6.5.5.  This issue might cause the backup of a large number of databases to become unreliable and skip databases.</p>
<p><a href="http://seer.entsupport.symantec.com/docs/330033.htm" target="_blank">Read the full Document here.</a></p>
<p>We have seen this behavior on a few systems, and found that carving up the backups into smaller batch files has solved the issue for us but we plan to move back to large batch files with the upcoming 6.5.6 update in Q2 of 2010.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/11/symantec-doc-id-330033-mssql-netbackup-db-backup-skipped/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware ESX4 Update 01 Removed from Update Manager</title>
		<link>http://wjpatton.com/index.php/2009/11/vmware-esx4-update-01-removed-from-update-manager/</link>
		<comments>http://wjpatton.com/index.php/2009/11/vmware-esx4-update-01-removed-from-update-manager/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 18:35:34 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX4]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=206</guid>
		<description><![CDATA[If you are looking to update your ESX4 hosts to Update 01, don&#8217;t look in Update Manager.  VMware has removed the update because of a bug with the HP Management Agents preventing the update from completely successfully and rendering the host inoperable.
From KB1016070:
&#8220;Note: If you want to install the update, you must download the update manually. [...]]]></description>
			<content:encoded><![CDATA[<p>If you are looking to update your ESX4 hosts to Update 01, don&#8217;t look in Update Manager.  VMware has removed the update because of a bug with the HP Management Agents preventing the update from completely successfully and rendering the host inoperable.</p>
<p>From <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1016070" target="_blank">KB1016070</a>:</p>
<p>&#8220;<strong>Note</strong>: If you want to install the update, you must download the update manually. The update is no longer available for automatic download in Update Manager and the vSphere Update Utility. You can find the update on the <a href="http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vsphere_4/4" target="_blank">VMware Downloads</a> site and copy the download to your local depot as needed.&#8221;</p>
<p>Note:  ESXi 4 is unaffected by this KB.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/11/vmware-esx4-update-01-removed-from-update-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1016070 &#8211; ESX 4 Update 01 and HP Management Agents Failed Upgrade</title>
		<link>http://wjpatton.com/index.php/2009/11/vmware-kb1016070-esx-4-update-01-and-hp-management-agents-failed-upgrade/</link>
		<comments>http://wjpatton.com/index.php/2009/11/vmware-kb1016070-esx-4-update-01-and-hp-management-agents-failed-upgrade/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 18:26:12 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[KB]]></category>
		<category><![CDATA[SIM]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=204</guid>
		<description><![CDATA[VMware has posted a bug when upgrading ESX 4 to Update 01 with HP Management Agents running.  (ESXi is unaffected)
You may have your host end the update unsuccessfully, and in a non-responsive state.  To avoid this, disable all the HP Management Agents prior to running the update.
Read the full article here.
]]></description>
			<content:encoded><![CDATA[<p>VMware has posted a bug when upgrading ESX 4 to Update 01 with HP Management Agents running.  (ESXi is unaffected)</p>
<p>You may have your host end the update unsuccessfully, and in a non-responsive state.  To avoid this, disable all the HP Management Agents prior to running the update.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1016070" target="_blank">Read the full article here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/11/vmware-kb1016070-esx-4-update-01-and-hp-management-agents-failed-upgrade/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
