<?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>VMdamentals</title>
	<atom:link href="http://www.vmdamentals.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.vmdamentals.com</link>
	<description>VMware Technical Deepdive by Erik Zandboer</description>
	<lastBuildDate>Fri, 27 Aug 2010 08:04:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>PHD Virtual Backup software with XenServer support: One down, ESXi to go</title>
		<link>http://www.vmdamentals.com/?p=607</link>
		<comments>http://www.vmdamentals.com/?p=607#comments</comments>
		<pubDate>Fri, 27 Aug 2010 08:04:35 +0000</pubDate>
		<dc:creator>Erik Zandboer</dc:creator>
				<category><![CDATA[esXpress]]></category>
		<category><![CDATA[Backup]]></category>
		<category><![CDATA[Citrix XenServer]]></category>
		<category><![CDATA[PHDvirtual]]></category>
		<category><![CDATA[Virtual Backup]]></category>
		<category><![CDATA[virtual disk backup]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[Xen]]></category>
		<category><![CDATA[XenServer]]></category>

		<guid isPermaLink="false">http://www.vmdamentals.com/?p=607</guid>
		<description><![CDATA[PHDvirtual, creators of the backup product for VMware environments formerly known as esXpress, have introduced a new version of their PHD Virtual Backup software with support for Citrix XenServer backups.]]></description>
		<wfw:commentRss>http://www.vmdamentals.com/?feed=rss2&amp;p=607</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>vSphere 4.1 and virtual disk names</title>
		<link>http://www.vmdamentals.com/?p=602</link>
		<comments>http://www.vmdamentals.com/?p=602#comments</comments>
		<pubDate>Wed, 18 Aug 2010 06:10:30 +0000</pubDate>
		<dc:creator>Erik Zandboer</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Backup]]></category>
		<category><![CDATA[naming convention]]></category>
		<category><![CDATA[Virtual Backup]]></category>
		<category><![CDATA[virtual disk]]></category>
		<category><![CDATA[vmdk naming]]></category>
		<category><![CDATA[vSphere 4.1]]></category>

		<guid isPermaLink="false">http://www.vmdamentals.com/?p=602</guid>
		<description><![CDATA[I just spotted something that had not occurred to me yet... A small new detail in vSphere 4.1 (or I just missed out on it previously)... VMware has had this "problem" for a long time: If you added a second virtual disk to a virtual machine on a datastore different from the first virtual disk, vSphere used to name that new virtual disk the same as the base disk. Well not any more!
]]></description>
		<wfw:commentRss>http://www.vmdamentals.com/?feed=rss2&amp;p=602</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>vCenter 4.1 and CPU usage</title>
		<link>http://www.vmdamentals.com/?p=594</link>
		<comments>http://www.vmdamentals.com/?p=594#comments</comments>
		<pubDate>Fri, 23 Jul 2010 08:33:26 +0000</pubDate>
		<dc:creator>Erik Zandboer</dc:creator>
				<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://www.vmdamentals.com/?p=594</guid>
		<description><![CDATA[I have a very tiny testing environment, which I just upgraded to vSphere 4.1. I chose to reinstall the vCenter server on a 64bit Windows 2003 VM with a local SQL express installation, having only 1GB of memory and a single vCPU. I know this is against best practice, but I like to follow the [...]]]></description>
		<wfw:commentRss>http://www.vmdamentals.com/?feed=rss2&amp;p=594</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
