<?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>Moki Systems Blog &#187; VMWare</title>
	<atom:link href="http://www.mokisystems.com/blog/category/vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mokisystems.com/blog</link>
	<description>Addressing such topics as: web programming, design, ruby on rails, cake php, postgresql, linux, seo</description>
	<lastBuildDate>Thu, 19 Aug 2010 00:18:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How We&#8217;re Using VMWare Server</title>
		<link>http://www.mokisystems.com/blog/how-were-using-vmware-server/</link>
		<comments>http://www.mokisystems.com/blog/how-were-using-vmware-server/#comments</comments>
		<pubDate>Tue, 15 Jul 2008 18:23:47 +0000</pubDate>
		<dc:creator>mark</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[System Administration]]></category>
		<category><![CDATA[VMWare]]></category>

		<guid isPermaLink="false">http://beta.mokisystems.com/blog/?p=9</guid>
		<description><![CDATA[VMWare releasing a free version of their server virtualization product opened up some possibilities for us. Moki Systems had multiple servers performing a variety of tasks but there were things we didn&#8217;t have. We didn&#8217;t have a split between production and development servers and we didn&#8217;t have good utilization. Low CPU and memory utilization offers [...]]]></description>
			<content:encoded><![CDATA[<p>VMWare releasing a free version of their server virtualization product opened up some possibilities for us. Moki Systems had multiple servers performing a variety of tasks but there were things we didn&#8217;t have. We didn&#8217;t have a split between production and development servers and we didn&#8217;t have good utilization. Low CPU and memory utilization offers a comfort level but it adds costs, especially when you need more servers that cost money, use electricity, and generate heat.</p>
<p>Free VMWare server limits running virtual servers to 4. Our solution was to purchase new servers  equipped with 1 SATA disk for the OS and 4 SCSI disks, 1 for each virtual machine (VM). While VMWare offers an option to write to the disk directly I opted not to do that because the virtual disk files VMWare uses make your VM&#8217;s highly portable and easy to duplicate. Disaster recovery practice becomes far easier when you can easily make a duplicate of your production server.</p>
<p>This architecture&#8217;s utility was brought to light when one of your servers died. We were able to pull the disks containing our production servers, copy the VM&#8217;s to another server, then get those servers running again quickly. There was no need for OS reinstall or recovery from backup and because of this portability downtime was minimized.</p>
<p>I have VMWare server installed on my Windows workstation with a Centos 5 VM running in the background. I use it for some MySQL and PHP stuff so it isn&#8217;t used a whole lot but I hardly know it&#8217;s there. The beauty of this that the Windows guys can have a Linux VM and the Linux guys can have a Windows VM. That can help quite a bit when testing browser compatibility on a website or getting access to a tool not available for your OS of choice.</p>
<p>VMWare server has helped us utilize our server resources better at a very minimal cost. Running 4 servers for the price of one saves us time and money. What else could you ask for?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mokisystems.com/blog/how-were-using-vmware-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
