<?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>Ubiquitous Talk &#187; automated</title>
	<atom:link href="http://blog.laspina.ca/ubiquitous/tag/automated/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.laspina.ca</link>
	<description>Blogging for technical minds.</description>
	<lastBuildDate>Mon, 31 May 2010 04:29:47 +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>Protecting ESX VMFS Stores with Automation</title>
		<link>http://blog.laspina.ca/ubiquitous/protecting-esx-vmfs-stores-with-automation</link>
		<comments>http://blog.laspina.ca/ubiquitous/protecting-esx-vmfs-stores-with-automation#comments</comments>
		<pubDate>Mon, 30 Mar 2009 03:31:48 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[automated]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[cron]]></category>
		<category><![CDATA[scripts]]></category>
		<category><![CDATA[undelete]]></category>
		<category><![CDATA[vmfs]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=98</guid>
		<description><![CDATA[Some time ago I shared some interesting information about VMFS volumes that I found using direct analysis in my blog named Understanding VMFS volumes. This spawned some discussions on the VMware Community forums and it became apparent that an automated backup of the critical VMFS info could be useful in the event of an undesirable security event that impacts our [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/protecting-esx-vmfs-stores-with-automation/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Automated VMware Tools upgrades using your VC and Perl</title>
		<link>http://blog.laspina.ca/ubiquitous/automated_vmware_tools_upgrades_using</link>
		<comments>http://blog.laspina.ca/ubiquitous/automated_vmware_tools_upgrades_using#comments</comments>
		<pubDate>Sun, 25 May 2008 06:45:09 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[automated]]></category>
		<category><![CDATA[reboot]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=53</guid>
		<description><![CDATA[I was upgrading a VI 2.0.2/3.0.2 system to VI 2.5/3.5 and found that upgrading VMware Tools was becoming a real pain. So I decided to look for a better way. I first did the usual search hoping to find a quickie but no luck. I searched the VMware forums to find that everyone was using the MSI package in a manner external to [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/automated_vmware_tools_upgrades_using/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
