<?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"
	>
<channel>
	<title>Comments on: More on restoring ESX from backup</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/virtualization-pro/more-on-restoring-esx-from-backup/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/more-on-restoring-esx-from-backup/</link>
	<description>A SearchVMware.com blog</description>
	<pubDate>Sat, 28 Nov 2009 06:08:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Sbeaver</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/more-on-restoring-esx-from-backup/#comment-106</link>
		<dc:creator>Sbeaver</dc:creator>
		<pubDate>Mon, 05 Jan 2009 16:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/virtualization-pro/?p=206#comment-106</guid>
		<description>Running the support script is a great idea and I also recommend running that script as soon as the ESX server is built so you have a base line to refer to.  

I am one of the true believers that ESX should never be restored and should always be rebuilt.  I like to preach that ESX is an appliance and should be treated as such.  If you have the a solid build process in place you should never really need to restore the server itself.  Most of my documentation is in the form of comments on my scripts.  If I make any changes to ESX I first add the change to my build scripts and then make the change in production.  

Automation is the key to great success

Steve Beaver</description>
		<content:encoded><![CDATA[<p>Running the support script is a great idea and I also recommend running that script as soon as the ESX server is built so you have a base line to refer to.  </p>
<p>I am one of the true believers that ESX should never be restored and should always be rebuilt.  I like to preach that ESX is an appliance and should be treated as such.  If you have the a solid build process in place you should never really need to restore the server itself.  Most of my documentation is in the form of comments on my scripts.  If I make any changes to ESX I first add the change to my build scripts and then make the change in production.  </p>
<p>Automation is the key to great success</p>
<p>Steve Beaver</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->