<?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: NAS Management</title>
	<atom:link href="http://blog.50micron.com/2006/10/17/nas-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.50micron.com/2006/10/17/nas-management/</link>
	<description>Ranting and raving about storage and technology</description>
	<lastBuildDate>Tue, 07 Sep 2010 00:28:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: SanGod</title>
		<link>http://blog.50micron.com/2006/10/17/nas-management/comment-page-1/#comment-48</link>
		<dc:creator>SanGod</dc:creator>
		<pubDate>Tue, 05 Dec 2006 05:32:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.sangod.com/?p=31#comment-48</guid>
		<description>We only have the one NS500G, it&#039;s kind of a toy but I have to admit has performed admirably with the 2.5TB of data we&#039;ve got behind it.  (And I just put in a P.O. for another 6TB usable to add to it for longer-term archiving.)

I could ask for some alert when the storage pool gets low.  I&#039;ve got my filesytems set to auto-extend when they hit 90% capacity, and I get an email when that happens, but it seems the only way I am notified that the Storage pool has filled is when I get the subsequent emails when a filesystem goes up beyond 90%.   (I seem to get one every percentage point the FS climbs)

The other thing I hate, is that in order to do a competent split-mirror backup I&#039;m going to need another NS501G (single datamover).  Because we can&#039;t use NDMP (Our company policy is Disk--&gt;disk--&gt;tape, and the &quot;disk--&gt;tape--&gt;disk&quot; process would be cumbersome at best) I&#039;m stuck dedicating a single Gig-E port for backups, exporting the filesystems down that port, and backing them up as \\server\c$\filesystem\* , which is just not the quickest way to run backups when there are better alternatives.  A snap backup to an NS501 followed by sucking the backup down a 4G etherchannel would at least be marginally better.

It&#039;s about time Veritas gets with EMC and writes a Celerra agent for NBU don&#039;t you think?</description>
		<content:encoded><![CDATA[<p>We only have the one NS500G, it&#8217;s kind of a toy but I have to admit has performed admirably with the 2.5TB of data we&#8217;ve got behind it.  (And I just put in a P.O. for another 6TB usable to add to it for longer-term archiving.)</p>
<p>I could ask for some alert when the storage pool gets low.  I&#8217;ve got my filesytems set to auto-extend when they hit 90% capacity, and I get an email when that happens, but it seems the only way I am notified that the Storage pool has filled is when I get the subsequent emails when a filesystem goes up beyond 90%.   (I seem to get one every percentage point the FS climbs)</p>
<p>The other thing I hate, is that in order to do a competent split-mirror backup I&#8217;m going to need another NS501G (single datamover).  Because we can&#8217;t use NDMP (Our company policy is Disk&#8211;>disk&#8211;>tape, and the &#8220;disk&#8211;>tape&#8211;>disk&#8221; process would be cumbersome at best) I&#8217;m stuck dedicating a single Gig-E port for backups, exporting the filesystems down that port, and backing them up as \\server\c$\filesystem\* , which is just not the quickest way to run backups when there are better alternatives.  A snap backup to an NS501 followed by sucking the backup down a 4G etherchannel would at least be marginally better.</p>
<p>It&#8217;s about time Veritas gets with EMC and writes a Celerra agent for NBU don&#8217;t you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SanMan</title>
		<link>http://blog.50micron.com/2006/10/17/nas-management/comment-page-1/#comment-47</link>
		<dc:creator>SanMan</dc:creator>
		<pubDate>Tue, 28 Nov 2006 19:41:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.sangod.com/?p=31#comment-47</guid>
		<description>We have several Celerra NS704Gs in our infrastructure. 4 data movers with Clariion and Symm backends. They are a real beast to set up and we have recently tried deploying MPFS (HighRoad). Eeeek! I&#039;d say Celerras (even the non-gateway appliances) are way too much overhead for most companies and EMC has to make their homogeneous software work with what sells in the market place. EMC has straight up fiber channel down but their NAS stuff could use some work...</description>
		<content:encoded><![CDATA[<p>We have several Celerra NS704Gs in our infrastructure. 4 data movers with Clariion and Symm backends. They are a real beast to set up and we have recently tried deploying MPFS (HighRoad). Eeeek! I&#8217;d say Celerras (even the non-gateway appliances) are way too much overhead for most companies and EMC has to make their homogeneous software work with what sells in the market place. EMC has straight up fiber channel down but their NAS stuff could use some work&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SanGod</title>
		<link>http://blog.50micron.com/2006/10/17/nas-management/comment-page-1/#comment-23</link>
		<dc:creator>SanGod</dc:creator>
		<pubDate>Tue, 17 Oct 2006 23:22:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.sangod.com/?p=31#comment-23</guid>
		<description>I&#039;d thought of that, but EMC doesn&#039;t usually sell *JUST* ECC, it&#039;s usually part of a package. (Of course, if you bought a Symm for the big storage and NetApp for the NFS/CIFS storage, you&#039;d be in the ball park.

Besides - when you&#039;re produce hardware *AND* software, you always support your own hardware first, then build in the competitors stuff to keep the heterogenious customers happy.

ECC&#039;s management of Clariion is spotty at best, andÂ using a Symm for NAS is like killing a mosquito with a cannon-ball. You&#039;re throwing way too much VERY EXPENSIVE storage at a system that will never be able to utilize the performance.

I can&#039;t say I&#039;m unhappy with Celerra as a file-server. We have a single data-mover pushing over 2TB of filesystems out to the network right now.</description>
		<content:encoded><![CDATA[<p>I&#8217;d thought of that, but EMC doesn&#8217;t usually sell *JUST* ECC, it&#8217;s usually part of a package. (Of course, if you bought a Symm for the big storage and NetApp for the NFS/CIFS storage, you&#8217;d be in the ball park.</p>
<p>Besides &#8211; when you&#8217;re produce hardware *AND* software, you always support your own hardware first, then build in the competitors stuff to keep the heterogenious customers happy.</p>
<p>ECC&#8217;s management of Clariion is spotty at best, andÂ using a Symm for NAS is like killing a mosquito with a cannon-ball. You&#8217;re throwing way too much VERY EXPENSIVE storage at a system that will never be able to utilize the performance.</p>
<p>I can&#8217;t say I&#8217;m unhappy with Celerra as a file-server. We have a single data-mover pushing over 2TB of filesystems out to the network right now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Storagezilla</title>
		<link>http://blog.50micron.com/2006/10/17/nas-management/comment-page-1/#comment-22</link>
		<dc:creator>Storagezilla</dc:creator>
		<pubDate>Tue, 17 Oct 2006 22:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.sangod.com/?p=31#comment-22</guid>
		<description>Or it means ECC is very popular in NetApp shops. One wonders if it might be *more* popular amongst NetApp customers than Storage Suite. ;)</description>
		<content:encoded><![CDATA[<p>Or it means ECC is very popular in NetApp shops. One wonders if it might be *more* popular amongst NetApp customers than Storage Suite. <img src='http://blog.50micron.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
