<?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: Should Virtual Center run as a Virtual Machine?</title>
	<atom:link href="http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Wed, 25 Jan 2012 13:41:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Design Challenges Of Virtualized vCenter With A vNetwork Distributed Switch &#124; VM /ETC</title>
		<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/comment-page-2/#comment-4167</link>
		<dc:creator>Design Challenges Of Virtualized vCenter With A vNetwork Distributed Switch &#124; VM /ETC</dc:creator>
		<pubDate>Mon, 08 Mar 2010 02:42:40 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=178#comment-4167</guid>
		<description>[...] brought up the logistical argument about the brains of the virtual infrastructure running in the environment it is managing before. [...]</description>
		<content:encoded><![CDATA[<p>[...] brought up the logistical argument about the brains of the virtual infrastructure running in the environment it is managing before. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware PEX2010: Night of Nines and Saturday Random Thoughts &#124; VM /ETC</title>
		<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/comment-page-2/#comment-4052</link>
		<dc:creator>VMware PEX2010: Night of Nines and Saturday Random Thoughts &#124; VM /ETC</dc:creator>
		<pubDate>Sun, 07 Feb 2010 14:26:24 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=178#comment-4052</guid>
		<description>[...] database be separated from the virtualized vCenter Server, however. Although VMware supported but never seemed to take definitive sides on a virtual versus a physical VirtualCenter 2.x in the past, it is [...]</description>
		<content:encoded><![CDATA[<p>[...] database be separated from the virtualized vCenter Server, however. Although VMware supported but never seemed to take definitive sides on a virtual versus a physical VirtualCenter 2.x in the past, it is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why not VirtualCenter with SQL 2005 Express? &#124; VM /ETC</title>
		<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/comment-page-2/#comment-2853</link>
		<dc:creator>Why not VirtualCenter with SQL 2005 Express? &#124; VM /ETC</dc:creator>
		<pubDate>Sun, 09 Aug 2009 13:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=178#comment-2853</guid>
		<description>[...] as a VM &#8211; A lot of SMBs choose to run VC as a VM. If you follow best practices then you should separate the SQL instance from the VC server. However, I&#8217;m willing to bet the [...]</description>
		<content:encoded><![CDATA[<p>[...] as a VM &#8211; A lot of SMBs choose to run VC as a VM. If you follow best practices then you should separate the SQL instance from the VC server. However, I&#8217;m willing to bet the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware vCenter &#38; SQL server best practices &#124; Virtualfuture.info</title>
		<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/comment-page-2/#comment-1932</link>
		<dc:creator>VMware vCenter &#38; SQL server best practices &#124; Virtualfuture.info</dc:creator>
		<pubDate>Mon, 26 Jan 2009 19:56:22 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=178#comment-1932</guid>
		<description>[...] VC Virtual ? @ Rich Brambly (VMETC) : http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/ Physical/Virtual discussion @ VIOps : http://viops.vmware.com/home/message/1359 Again, I&#8217;m [...]</description>
		<content:encoded><![CDATA[<p>[...] VC Virtual ? @ Rich Brambly (VMETC) : <a href="http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/" rel="nofollow">http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/</a> Physical/Virtual discussion @ VIOps : <a href="http://viops.vmware.com/home/message/1359" rel="nofollow">http://viops.vmware.com/home/message/1359</a> Again, I&#8217;m [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adias</title>
		<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/comment-page-2/#comment-1743</link>
		<dc:creator>adias</dc:creator>
		<pubDate>Wed, 31 Dec 2008 12:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=178#comment-1743</guid>
		<description>Yes, you can run it there but you should have a backup, physical or virtual. We run the main one in the esx cluster but also keep a nightly clone on a seperate esx server that is not part of the cluster.</description>
		<content:encoded><![CDATA[<p>Yes, you can run it there but you should have a backup, physical or virtual. We run the main one in the esx cluster but also keep a nightly clone on a seperate esx server that is not part of the cluster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adias</title>
		<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/comment-page-2/#comment-5023</link>
		<dc:creator>adias</dc:creator>
		<pubDate>Wed, 31 Dec 2008 12:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=178#comment-5023</guid>
		<description>Yes, you can run it there but you should have a backup, physical or virtual. We run the main one in the esx cluster but also keep a nightly clone on a seperate esx server that is not part of the cluster.</description>
		<content:encoded><![CDATA[<p>Yes, you can run it there but you should have a backup, physical or virtual. We run the main one in the esx cluster but also keep a nightly clone on a seperate esx server that is not part of the cluster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fabio Arnò</title>
		<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/comment-page-2/#comment-1741</link>
		<dc:creator>Fabio Arnò</dc:creator>
		<pubDate>Wed, 31 Dec 2008 11:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=178#comment-1741</guid>
		<description>IMHO pushing too far consolidataion isn&#039;t that big deal: we&#039;re talking about benefits coming from the virtualization of a single host (VC) ?
I&#039;m rather more concerned about performance and possible issues.
But some benefits could be gained running VC on a VM too (HA benefits).

What about having VC on a physical host (with its DB on external storage, in SAN for instance) and a standby VM (off) ready to take its place for failover ?
Of course, should the physical host on which our VC is running go down, to failover on the ready-VM we should first configure it to see LUNs owned by the VC.</description>
		<content:encoded><![CDATA[<p>IMHO pushing too far consolidataion isn&#8217;t that big deal: we&#8217;re talking about benefits coming from the virtualization of a single host (VC) ?<br />
I&#8217;m rather more concerned about performance and possible issues.<br />
But some benefits could be gained running VC on a VM too (HA benefits).</p>
<p>What about having VC on a physical host (with its DB on external storage, in SAN for instance) and a standby VM (off) ready to take its place for failover ?<br />
Of course, should the physical host on which our VC is running go down, to failover on the ready-VM we should first configure it to see LUNs owned by the VC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fabio Arnò</title>
		<link>http://vmetc.com/2007/12/28/should-virtual-center-run-as-a-virtual-machine/comment-page-1/#comment-5022</link>
		<dc:creator>Fabio Arnò</dc:creator>
		<pubDate>Wed, 31 Dec 2008 11:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=178#comment-5022</guid>
		<description>IMHO pushing too far consolidataion isn&#039;t that big deal: we&#039;re talking about benefits coming from the virtualization of a single host (VC) ?
I&#039;m rather more concerned about performance and possible issues.
But some benefits could be gained running VC on a VM too (HA benefits).

What about having VC on a physical host (with its DB on external storage, in SAN for instance) and a standby VM (off) ready to take its place for failover ?
Of course, should the physical host on which our VC is running go down, to failover on the ready-VM we should first configure it to see LUNs owned by the VC.</description>
		<content:encoded><![CDATA[<p>IMHO pushing too far consolidataion isn&#8217;t that big deal: we&#8217;re talking about benefits coming from the virtualization of a single host (VC) ?<br />
I&#8217;m rather more concerned about performance and possible issues.<br />
But some benefits could be gained running VC on a VM too (HA benefits).</p>
<p>What about having VC on a physical host (with its DB on external storage, in SAN for instance) and a standby VM (off) ready to take its place for failover ?<br />
Of course, should the physical host on which our VC is running go down, to failover on the ready-VM we should first configure it to see LUNs owned by the VC.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

