<?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>Malaysia VMware Communities &#187; netapps</title>
	<atom:link href="http://malaysiavm.com/blog/tag/netapps/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 21 Nov 2011 15:50:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>FC NFS ISCSI</title>
		<link>http://malaysiavm.com/blog/fc-nfs-iscsi/</link>
		<comments>http://malaysiavm.com/blog/fc-nfs-iscsi/#comments</comments>
		<pubDate>Mon, 05 Jan 2009 03:29:26 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[FC]]></category>
		<category><![CDATA[Fiber Channel]]></category>
		<category><![CDATA[ISCSI]]></category>
		<category><![CDATA[netapps]]></category>
		<category><![CDATA[nfs]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=752</guid>
		<description><![CDATA[There had been numbers of review and discussion regarding the choices of storage for us to run on Virtual Environment today. I believed that the hot discussion is always moving talk about the right storage with right design and implementation to the VM farm always. The most hottest topic are still regarding the NFS, ISCSI [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"><!--
google_ad_client = "pub-7430566020196385";
/* MVM Index Link Code 468x15, created 1/3/10 */
google_ad_slot = "5937837755";
google_ad_width = 468;
google_ad_height = 15;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p><p>There had been numbers of review and discussion regarding the choices of storage for us to run on Virtual Environment today. I believed that the hot discussion is always moving talk about the right storage with right design and implementation to the VM farm always. The most hottest topic are still regarding the <a href="http://malaysiavm.com/blog/tag/nfs">NFS</a>, <a href="http://malaysiavm.com/blog/tag/iscsi">ISCSI</a> and <a href="http://malaysiavm.com/blog/tag/fc">FC</a> implementation which provide better features, performance and reliability.</p>
<p>Personally, I had 3 of it running in my environment now and of course, I had spent a huge number of times to really test out all the solution and compare apple to apple to further study of my requirement. Here are some reading I get from my test for 3 solution above.</p>
<p><span id="more-752"></span></p>
<p>For I/O performance, I am using the <a href="http://malaysiavm.com/blog/tag/io">IO</a> meter as to generate the max output to the storage. I manage to get 190MB/s for my FC storage on 100 % read, and I only managed to get the output of 170MB/s on ISCSI, but on NFS, I only managed to get at 125MB/s. If we look at the number here, and compare to my high load <a href="http://www.malaysiavm.com/blog/tag/r900">R900</a> ESX host, actually it is more than enough to handle the number of <a href="http://www.malaysiavm.com/blog/tag/vm">VM</a> I have in the ESX host. There are a lot of article introduce NFS, and the features of Netapps, but remember, <a href="http://www.malaysiavm.com/blog/tag/esx">ESX</a> itself had improved from time to time. Thin Provisioning is no longer new thing, as you may get it with many vendor today by free as well as volume snap. But Dedupe will still be an interesting technology in netapps. If we look at FC, you will mostly lose all this technology, but it provide a stable performance as you need to virtualize some heavy environment moving forward. I am currently still test out the storage solution before I decide to go with a final choice. I will suggest to keep an eye on the technology trend as we may also remember that the <a href="http://www.malaysiavm.com/blog/tag/vmware">VMware</a> <a href="http://www.malaysiavm.com/blog/tag/esx4">ESX 4</a> is on the way, which may change the game of storage strategy significantly.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/fc-nfs-iscsi/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Storage Planning &#8211; Virtualization</title>
		<link>http://malaysiavm.com/blog/storage-planning-virtualization/</link>
		<comments>http://malaysiavm.com/blog/storage-planning-virtualization/#comments</comments>
		<pubDate>Wed, 10 Sep 2008 05:35:47 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[datacenter]]></category>
		<category><![CDATA[EMC]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[ISCSI]]></category>
		<category><![CDATA[netapps]]></category>
		<category><![CDATA[nfs]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=246</guid>
		<description><![CDATA[Storage is always the important piece to be run in Data center as well as any solutions we put into the production environment. It will also impact the capacity planning, performance as well as the sustainable period of the specify solution. Here I would like to specify talk about ESX storage planning. As many of [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"><!--
google_ad_client = "pub-7430566020196385";
/* MVM Index Link Code 468x15, created 1/3/10 */
google_ad_slot = "5937837755";
google_ad_width = 468;
google_ad_height = 15;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p><p>Storage is always the important piece to be run in <a href="http://malaysiavm.com/blog/tag/datacenter">Data center</a> as well as any solutions we put into the production environment. It will also impact the capacity planning, performance as well as the sustainable period of the specify solution.</p>
<p>Here I would like to specify talk about <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> storage planning. As many of the cases I read and experience before, more and more users are really heading to the stage of choosing specify storage for specify solutions. Example you may think off for using <a href="http://malaysiavm.com/blog/tag/netapps">Netapps</a> on <a href="http://malaysiavm.com/blog/tag/nfs">NFS</a> for ESX, which claim better performance, dedupe and protocol different. Somehow, the users had forgotten that they had not run any of netapps storage in their existing environment. When we look at the management perspective, the operation management for IT support is not SIMPLIFY. Everyone know how important to standardize our environment as well as simplify out IT environment. The more complex you have, the more pain you will feel.</p>
<p><span id="more-246"></span><br />
<a href="http://malaysiavm.com/blog/tag/esx">ESX</a> had been design to run on multiple different range, different brand, as well as different type of protocol of storage in the market today. The reason of this is able to provide users a number of choices to be choose for deployment which may really fit the existing environment. Most users are now been looking at the storage specifically for Virtualization, that was really due to the marketing strategy or brochure been always claim the specify products will gain better performance. If you are the storage guys in your IT department, maybe you should consider what will be the best fit for your environment VS what is the coolest technology in the world for VMware.</p>
<p>Let talk about 1 scenario here, a user who had existing running with cx3-80 <a href="http://malaysiavm.com/blog/tag/emc">EMC</a> SAN storage with all fiber switches ready. The storage is only 50% populated. The storage guys had raised the request to bring in the latest ISCSI technology from netapps and Equal logic. When it does the price comparison, the TCO and implementation cost of ISCSI become too huge different VS extending the enclosure on cx3-80. Back to real world, I am really curious that if <a href="http://malaysiavm.com/blog/tag/san">SAN</a> Fiber storage will be poor perform and inconsistent compare to ISCSI if you have everything setup and configure correctly in your fiber SAN. Most of the case is NO. As in my POC test, I can see that the performances on the Fiber are still better and stable.</p>
<p><a href="http://malaysiavm.com/blog/tag/iscsi">ISCSI</a> is really simple and easier manage, but somehow, there are many technical details that require redeploying the entire environment to gain the peak performance you expected. That is definitely an advice at the end you will get from the vendor. Therefore, a best fit storage for your own environment is more important always. You should look at CAPEX vs OPEX when you plan the storage for virtualization.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/storage-planning-virtualization/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.433 seconds -->

