<?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: Stop, NetApp, You&#8217;re Killing Me</title>
	<atom:link href="http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/feed/" rel="self" type="application/rss+xml" />
	<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/</link>
	<description>qstat -u aleonard -s z</description>
	<lastBuildDate>Tue, 07 Feb 2012 15:27:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Goid</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-3697</link>
		<dc:creator>Goid</dc:creator>
		<pubDate>Tue, 24 Jan 2012 18:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-3697</guid>
		<description>Here we are in 2011, the FAS2020, the price point box Netapp was selling last year, can&#039;t be upgraded to 64-bit ONTAP, thus we still have the limitation of 1 TB A-SIS.

I suggest for anyone considering Netapp as their new storage vendor, really look into the product. Don&#039;t trust the reseller or Netapp, you have to do your own work. 2 months in to our Netapp fiasco I realized I should have Googled &quot;limitations of the Netapp FAS2020&quot;. I found about this after the reseller told me it was a limitation of the OS that will never change, because the box can&#039;t support the 64-bit OS. I never saw a single document indicating this. I read of limitations, but none indicated the FAS2020 wouldn&#039;t support ONTAP 8 (64-BIT). We wouldn&#039;t have purchased this piece of crap knowing this. And the best part is, our Netapp rep said they could do a convenient buy-back option on the 2020 for one of the newer models. The funny thing is this device is 1 year old and they wanted to slap a 75% depreciation on it. They would offer us 25% off the new array if we swapped it.

It&#039;s funny too, cause for several weeks our Netapp rep kept asking why we weren&#039;t upgrading to ONTAP 8, when I told him the 2020A doesn&#039;t support it, he stopped asking about it. So sales doesn&#039;t even know about this. This is the low-end model, so they don&#039;t care about it, just get it out the door.

I like the Netapp product and I do see value in it, however any potential ROI on this product is negated by the training required to administer the product and the disk space you lose to Netapp &quot;features&quot;.

I guess as long as you have money to burn and don&#039;t buy their lowest option, Netapp is a great product.

If you are looking at Netapp, research everything before you even let them know you are looking.

And I will say this, Tier 1 support blows, you might as well just use Google. Unless your system is down, they are useless.

If you read Dave Hitz&#039; book, you would realize that from the very beginning Netapp was all about sales. It is apparent the companies philosophy was Sell it, no matter how limited the product is.

I suggest reading &quot;How to Castrate a Bull&quot; to get the real Netapp story.</description>
		<content:encoded><![CDATA[<p>Here we are in 2011, the FAS2020, the price point box Netapp was selling last year, can&#8217;t be upgraded to 64-bit ONTAP, thus we still have the limitation of 1 TB A-SIS.</p>
<p>I suggest for anyone considering Netapp as their new storage vendor, really look into the product. Don&#8217;t trust the reseller or Netapp, you have to do your own work. 2 months in to our Netapp fiasco I realized I should have Googled &#8220;limitations of the Netapp FAS2020&#8243;. I found about this after the reseller told me it was a limitation of the OS that will never change, because the box can&#8217;t support the 64-bit OS. I never saw a single document indicating this. I read of limitations, but none indicated the FAS2020 wouldn&#8217;t support ONTAP 8 (64-BIT). We wouldn&#8217;t have purchased this piece of crap knowing this. And the best part is, our Netapp rep said they could do a convenient buy-back option on the 2020 for one of the newer models. The funny thing is this device is 1 year old and they wanted to slap a 75% depreciation on it. They would offer us 25% off the new array if we swapped it.</p>
<p>It&#8217;s funny too, cause for several weeks our Netapp rep kept asking why we weren&#8217;t upgrading to ONTAP 8, when I told him the 2020A doesn&#8217;t support it, he stopped asking about it. So sales doesn&#8217;t even know about this. This is the low-end model, so they don&#8217;t care about it, just get it out the door.</p>
<p>I like the Netapp product and I do see value in it, however any potential ROI on this product is negated by the training required to administer the product and the disk space you lose to Netapp &#8220;features&#8221;.</p>
<p>I guess as long as you have money to burn and don&#8217;t buy their lowest option, Netapp is a great product.</p>
<p>If you are looking at Netapp, research everything before you even let them know you are looking.</p>
<p>And I will say this, Tier 1 support blows, you might as well just use Google. Unless your system is down, they are useless.</p>
<p>If you read Dave Hitz&#8217; book, you would realize that from the very beginning Netapp was all about sales. It is apparent the companies philosophy was Sell it, no matter how limited the product is.</p>
<p>I suggest reading &#8220;How to Castrate a Bull&#8221; to get the real Netapp story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-236</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Wed, 15 Jul 2009 21:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-236</guid>
		<description>Matt (or anyone) what sort of dedup throughput rates are you seeing in MB/sec on your FAS2050 (I guess it makes sense to run one dedup process per controller in most cases, or is anyone boldly running 8?)
Thanks</description>
		<content:encoded><![CDATA[<p>Matt (or anyone) what sort of dedup throughput rates are you seeing in MB/sec on your FAS2050 (I guess it makes sense to run one dedup process per controller in most cases, or is anyone boldly running 8?)<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-201</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 23 Feb 2009 08:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-201</guid>
		<description>I&#039;m way late on this one, but anyway:

Andy &amp; Jim: Re the A-SIS limit, with all due respect, if you bought un-aware of this limit then you didn&#039;t do your due diligence. Yes, your reseller /definately/ should have mentioned it, but beyond that the limits were/are not exactly hidden - we bought a FAS2050 in June 08 and I remember the A-SIS limits being mentioned in multiple, prominent places (spec sheets, docs explaining A-SIS, etc.) while doing my research. At least 7.3.1 is out now so the limits have been raised somewhat!

diemsi - 14 x 1 TB disks for 2.72 TB usable? I think you&#039;re doing something wrong there. Even if you follow &quot;best practice&quot; to the letter (RAID-DP, 2 hotspares) that should be more like 7TB available.

My 2 cents overall: We have a 2050 and I /love/ it, although admittedly I don&#039;t have a lot to benchmark against it. It&#039;s fast and expandable (for a company our size), A-SIS is achieving over 60% (!) average space saving across our volumes which equates to a lot of extra &quot;free&quot; storage, and NetApp snapshots are a huge time and effort saver.</description>
		<content:encoded><![CDATA[<p>I&#8217;m way late on this one, but anyway:</p>
<p>Andy &amp; Jim: Re the A-SIS limit, with all due respect, if you bought un-aware of this limit then you didn&#8217;t do your due diligence. Yes, your reseller /definately/ should have mentioned it, but beyond that the limits were/are not exactly hidden &#8211; we bought a FAS2050 in June 08 and I remember the A-SIS limits being mentioned in multiple, prominent places (spec sheets, docs explaining A-SIS, etc.) while doing my research. At least 7.3.1 is out now so the limits have been raised somewhat!</p>
<p>diemsi &#8211; 14 x 1 TB disks for 2.72 TB usable? I think you&#8217;re doing something wrong there. Even if you follow &#8220;best practice&#8221; to the letter (RAID-DP, 2 hotspares) that should be more like 7TB available.</p>
<p>My 2 cents overall: We have a 2050 and I /love/ it, although admittedly I don&#8217;t have a lot to benchmark against it. It&#8217;s fast and expandable (for a company our size), A-SIS is achieving over 60% (!) average space saving across our volumes which equates to a lot of extra &#8220;free&#8221; storage, and NetApp snapshots are a huge time and effort saver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James White</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-198</link>
		<dc:creator>James White</dc:creator>
		<pubDate>Tue, 17 Feb 2009 12:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-198</guid>
		<description>It&#039;s probably not recommended to have a 16TB aggregate as with that number of drives, even with RAID-DP the likelyhood of failure of the whole lot is higher.</description>
		<content:encoded><![CDATA[<p>It&#8217;s probably not recommended to have a 16TB aggregate as with that number of drives, even with RAID-DP the likelyhood of failure of the whole lot is higher.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: /kiwi</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-138</link>
		<dc:creator>/kiwi</dc:creator>
		<pubDate>Thu, 02 Oct 2008 10:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-138</guid>
		<description>If Netapp does not get A-SIS/Dedup sorted then check out Riverbeds new Atlas storage dedup devices when they come out of alpha/beta at the end of the year. Project named Corsica they are supposed to give up to 4x greater dedup than Netapp block level dedup due to the Riverbed byte level technology. We use both Riverbed AND Netapp and have to work around the multiple limits of dedup every day. It is very frustrating having a higher limit for dedup on one filer and then not being able to snapmirror to a slightly lower spec&#039;d head due to a different LOWER limit volume dedup setting!

I know the technology is new (ish) but some consistency across the board would be helpful when configuring/architecting storage solutions. so far we have 3TB for 3040, 1TB for 3020 and 0.5TB for 2020..... ??

Riverbed Atlas will be CIFS only dedup on release but is slated for NFS (VMware Datastores) soon after.

Good luck</description>
		<content:encoded><![CDATA[<p>If Netapp does not get A-SIS/Dedup sorted then check out Riverbeds new Atlas storage dedup devices when they come out of alpha/beta at the end of the year. Project named Corsica they are supposed to give up to 4x greater dedup than Netapp block level dedup due to the Riverbed byte level technology. We use both Riverbed AND Netapp and have to work around the multiple limits of dedup every day. It is very frustrating having a higher limit for dedup on one filer and then not being able to snapmirror to a slightly lower spec&#8217;d head due to a different LOWER limit volume dedup setting!</p>
<p>I know the technology is new (ish) but some consistency across the board would be helpful when configuring/architecting storage solutions. so far we have 3TB for 3040, 1TB for 3020 and 0.5TB for 2020&#8230;.. ??</p>
<p>Riverbed Atlas will be CIFS only dedup on release but is slated for NFS (VMware Datastores) soon after.</p>
<p>Good luck</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim S</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-72</link>
		<dc:creator>Jim S</dc:creator>
		<pubDate>Wed, 06 Aug 2008 19:30:58 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-72</guid>
		<description>We purchased a FAS2020 earlier this year.  Our reseller &quot;forgot&quot; to mention the 0.5TB volume limit for ASIS also.  However, this hasn&#039;t been much of a burden on us yet, although as we continue to expand our imaging systems it may be.  

We mostly use the filer to support our little VI3 infrastructure with a few RDMs for some SQL/Imaging servers.  Hopefully by the time we outgrow the 0.5TB limit Data OnTap 7.3 will be General Distribution release.  

Other than this &quot;oversight&quot; and the outrageous prices I&#039;m a big fan of NetApp.

I did find that it&#039;s much easier to shop for NetApp gear towards the end of NetApp&#039;s fiscal year/quarter.  They seem to actually negotiate on price then.</description>
		<content:encoded><![CDATA[<p>We purchased a FAS2020 earlier this year.  Our reseller &#8220;forgot&#8221; to mention the 0.5TB volume limit for ASIS also.  However, this hasn&#8217;t been much of a burden on us yet, although as we continue to expand our imaging systems it may be.  </p>
<p>We mostly use the filer to support our little VI3 infrastructure with a few RDMs for some SQL/Imaging servers.  Hopefully by the time we outgrow the 0.5TB limit Data OnTap 7.3 will be General Distribution release.  </p>
<p>Other than this &#8220;oversight&#8221; and the outrageous prices I&#8217;m a big fan of NetApp.</p>
<p>I did find that it&#8217;s much easier to shop for NetApp gear towards the end of NetApp&#8217;s fiscal year/quarter.  They seem to actually negotiate on price then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: diemsi</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-50</link>
		<dc:creator>diemsi</dc:creator>
		<pubDate>Fri, 04 Jul 2008 15:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-50</guid>
		<description>hi andy

i feel the same ! we have a new 2020 with a shelve (14x 1TB drives) at the end you just can use 2.72 TB - big joke

just my two cents

thx</description>
		<content:encoded><![CDATA[<p>hi andy</p>
<p>i feel the same ! we have a new 2020 with a shelve (14x 1TB drives) at the end you just can use 2.72 TB &#8211; big joke</p>
<p>just my two cents</p>
<p>thx</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-49</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Tue, 01 Jul 2008 14:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-49</guid>
		<description>Hi KPC,

Thanks for commenting again - I got a good chuckle out of your &quot;first&quot; storage comment.  My first storage array was a Digital StorageWorks box strung with a shared SCSI bus between two Sun servers in a HA cluster.  Ah, the (not so) good old days.

You have a good point about doing a PoC, but in light of that, your comment about needing a 3000-series head for a SnapVault secondary of 3000-series primaries is an interesting assertion.  We actually wound up moving from the 2020 to the 2050 purely because of the aggregate size limit (really, it does matter!), and the 2050 has worked admirably as a SnapVault secondary, A-SIS limitations aside.

I also disagree about RAID-4 being appropriate for a backup tier.  Given modern drive sizes and error rates - particularly with SATA drives - I think single-parity RAID is an idea whose time has come and gone.  But, then again, I realize that there are business situations where you need to do a cost-benefit analysis of things like single- versus double-parity RAID and the risks of data loss.

I may have been working with storage since the pre-fibre channel days, but I&#039;ve only been working with NetApp for a couple of years.  It&#039;s good to hear that they&#039;re keeping a long-term customer like yourself happy.  However, with more of an outsider&#039;s perspective, I see a company with a stagnant core product line and a next-gen version of ONTAP that&#039;s perpetually just over the horizon - and their last quarter financials weren&#039;t so hot, either.

Finally, I hope you&#039;re right that the end-user doesn&#039;t bear the brunt of the Sun-NetApp lawsuit.  We&#039;ll see soon enough, I suppose.</description>
		<content:encoded><![CDATA[<p>Hi KPC,</p>
<p>Thanks for commenting again &#8211; I got a good chuckle out of your &#8220;first&#8221; storage comment.  My first storage array was a Digital StorageWorks box strung with a shared SCSI bus between two Sun servers in a HA cluster.  Ah, the (not so) good old days.</p>
<p>You have a good point about doing a PoC, but in light of that, your comment about needing a 3000-series head for a SnapVault secondary of 3000-series primaries is an interesting assertion.  We actually wound up moving from the 2020 to the 2050 purely because of the aggregate size limit (really, it does matter!), and the 2050 has worked admirably as a SnapVault secondary, A-SIS limitations aside.</p>
<p>I also disagree about RAID-4 being appropriate for a backup tier.  Given modern drive sizes and error rates &#8211; particularly with SATA drives &#8211; I think single-parity RAID is an idea whose time has come and gone.  But, then again, I realize that there are business situations where you need to do a cost-benefit analysis of things like single- versus double-parity RAID and the risks of data loss.</p>
<p>I may have been working with storage since the pre-fibre channel days, but I&#8217;ve only been working with NetApp for a couple of years.  It&#8217;s good to hear that they&#8217;re keeping a long-term customer like yourself happy.  However, with more of an outsider&#8217;s perspective, I see a company with a stagnant core product line and a next-gen version of ONTAP that&#8217;s perpetually just over the horizon &#8211; and their last quarter financials weren&#8217;t so hot, either.</p>
<p>Finally, I hope you&#8217;re right that the end-user doesn&#8217;t bear the brunt of the Sun-NetApp lawsuit.  We&#8217;ll see soon enough, I suppose.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KPC</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-48</link>
		<dc:creator>KPC</dc:creator>
		<pubDate>Tue, 01 Jul 2008 01:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-48</guid>
		<description>I understand your concern.
But as we say devil is in the detail. Really true.

Be it any vendor or anyone....a sales person always claim everything can fly.
We here do a proof of concept before making a decision. 

In fact last year we did a PoC with other vendor NAS. They said it can achieve 300,000 iops.
End up our application can max get 40,000 iops. In the end it was a math that was about to do us in. There were multiple datamovers and they wanted us to use 8 filesystems across 8 datamovers to achieve that performance. Interesting confusing. End up it was a marketing hoax.

I think your FAS2020 is too low end for your environment. Looks like the reseller or person who size the system did not do it well. Your production being 3000 your snapvault should atleast be a min 3000. You are using storage for the first time looks like and this is pretty normal. If you try all the vendors in next 10 years, I tell you that you will feel NetApp was a better choice.

You can choose either raid-dp or raid-4. If you ask me a backup system can have raid4. So you gain lot of space. And snapreserves are the penalty you pay for quick restores. NetApp Snapshots are better than other online backup products. 

My suggession will be that you directly ask NetApp to size your system and plan for you. Resellers are not as smart as we think. With low-budget a vendor can directly help if you have a long term plan with them.

And for your concern on Sun and NetApp, Nothing will happen. These are two big companies and small patent things will not impact you and me. Even Sun has to buy NetApp they will have to spend over 10B$. Sun for most part of Storage has hardly had any success. They got Storagetek but did not leverage it well. On the other hand NetApp is doing extremely well. I think these two companies will settle it off the court. You see even the SSD disk provider STEC is sued by Seagate. This is pure play of commercial politics.</description>
		<content:encoded><![CDATA[<p>I understand your concern.<br />
But as we say devil is in the detail. Really true.</p>
<p>Be it any vendor or anyone&#8230;.a sales person always claim everything can fly.<br />
We here do a proof of concept before making a decision. </p>
<p>In fact last year we did a PoC with other vendor NAS. They said it can achieve 300,000 iops.<br />
End up our application can max get 40,000 iops. In the end it was a math that was about to do us in. There were multiple datamovers and they wanted us to use 8 filesystems across 8 datamovers to achieve that performance. Interesting confusing. End up it was a marketing hoax.</p>
<p>I think your FAS2020 is too low end for your environment. Looks like the reseller or person who size the system did not do it well. Your production being 3000 your snapvault should atleast be a min 3000. You are using storage for the first time looks like and this is pretty normal. If you try all the vendors in next 10 years, I tell you that you will feel NetApp was a better choice.</p>
<p>You can choose either raid-dp or raid-4. If you ask me a backup system can have raid4. So you gain lot of space. And snapreserves are the penalty you pay for quick restores. NetApp Snapshots are better than other online backup products. </p>
<p>My suggession will be that you directly ask NetApp to size your system and plan for you. Resellers are not as smart as we think. With low-budget a vendor can directly help if you have a long term plan with them.</p>
<p>And for your concern on Sun and NetApp, Nothing will happen. These are two big companies and small patent things will not impact you and me. Even Sun has to buy NetApp they will have to spend over 10B$. Sun for most part of Storage has hardly had any success. They got Storagetek but did not leverage it well. On the other hand NetApp is doing extremely well. I think these two companies will settle it off the court. You see even the SSD disk provider STEC is sued by Seagate. This is pure play of commercial politics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/comment-page-1/#comment-47</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 30 Jun 2008 19:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://andyleonard.com/2008/02/05/stop-netapp-youre-killing-me/#comment-47</guid>
		<description>Hi KPC,

    Glad to hear that NetApp is a good fit for you and your company - that&#039;s great, by all means, stick with what works for you!  I&#039;m also glad you found the piece funny - but I&#039;m only laughing on the outside.

    It sounds like our storage environment has different demands than yours.  I work for a relatively small, but growing, research non-profit.  When last I measured it, our data use was growing at a compound rate of about 8% each month; in other words, we double our storage use every nine months or so.  (As we&#039;re in the midst of a P2V project where direct-attached storage is moving to our NetApps, we&#039;re actually growing faster than that now, but that&#039;s a temporary bump.)  We already have multi-terabyte volumes - so, you do the math... the 16TB aggregate limit is a real problem for sites like us.

    It&#039;s also worth noting that a 16TB aggregate is not a 16TB file system available to a server.  750GB SATA drives become Rightsize 621 GB drives.  Then, for RAID-DP, subtract two disks out of each RAID group.  Next, there&#039;s the 10% WAFL overhead.  And don&#039;t forget to translate from marketing GB to real GB (or GB to GiB, if you will).  So that maximum-size 26-disk aggregate made up of 750GB drives winds up as 11.4TB.  And - of course - don&#039;t forget your snap reserves after that.

    As you mention, backups could be a challenge for large volumes; here&#039;s how we solve it: The 2020 in question was purchased as a SnapVault secondary.  Backups go from our primary 3040s to it, and then go via NDMP to tape for off-site/DR purposes.  The secondary tier gives us the extended backup window we need to get the data to tape and meet our DR requirements.  (I actually think this is a pretty common setup in this day and age.)

    Of course, I&#039;m not naive enough to think we can grow by adding drive shelves indefinitely (just added another one last Friday...).  My personal opinion is that we&#039;ll ultimately move to an HSM system, especially since much of the storage is used for instrument data (mass spec, microscopy, etc.) that is often difficult for researchers to categorize immediately as to its value.  The thought is to let the HSM algorithms find the appropriate tier for the data automatically.

    A couple other points:

    - If you re-read the blog post, you&#039;ll see that my main complaint with the 2020 was the lack of transparency with its limitations - and I know that I&#039;m not alone in this department.  (Heck, I just got a private email in the past week from a disappointed new 2020 owner.)  Yeah, it&#039;s low-end.  But working for a non-profit, without the sometimes cushy budgets of corporate IT, we&#039;ll buy what we can afford and push it hard; our funding agencies expect no less.  Getting blindsided by limitations that we didn&#039;t find out about during the sales process hurts.  Should we have done more due diligence?  Maybe, but the fact that we&#039;re not alone in being unhappy with the 2020 suggests there&#039;s a problem on the vendor side too.

    - I think you&#039;d do well to pay attention to the Sun/NetApp lawsuit.  We use both NetApp and ZFS here, and I&#039;m concerned that whichever side loses, it&#039;s going to have an impact on our operations.  I also think the lawsuit may have important implications for the storage industry as a whole.</description>
		<content:encoded><![CDATA[<p>Hi KPC,</p>
<p>    Glad to hear that NetApp is a good fit for you and your company &#8211; that&#8217;s great, by all means, stick with what works for you!  I&#8217;m also glad you found the piece funny &#8211; but I&#8217;m only laughing on the outside.</p>
<p>    It sounds like our storage environment has different demands than yours.  I work for a relatively small, but growing, research non-profit.  When last I measured it, our data use was growing at a compound rate of about 8% each month; in other words, we double our storage use every nine months or so.  (As we&#8217;re in the midst of a P2V project where direct-attached storage is moving to our NetApps, we&#8217;re actually growing faster than that now, but that&#8217;s a temporary bump.)  We already have multi-terabyte volumes &#8211; so, you do the math&#8230; the 16TB aggregate limit is a real problem for sites like us.</p>
<p>    It&#8217;s also worth noting that a 16TB aggregate is not a 16TB file system available to a server.  750GB SATA drives become Rightsize 621 GB drives.  Then, for RAID-DP, subtract two disks out of each RAID group.  Next, there&#8217;s the 10% WAFL overhead.  And don&#8217;t forget to translate from marketing GB to real GB (or GB to GiB, if you will).  So that maximum-size 26-disk aggregate made up of 750GB drives winds up as 11.4TB.  And &#8211; of course &#8211; don&#8217;t forget your snap reserves after that.</p>
<p>    As you mention, backups could be a challenge for large volumes; here&#8217;s how we solve it: The 2020 in question was purchased as a SnapVault secondary.  Backups go from our primary 3040s to it, and then go via NDMP to tape for off-site/DR purposes.  The secondary tier gives us the extended backup window we need to get the data to tape and meet our DR requirements.  (I actually think this is a pretty common setup in this day and age.)</p>
<p>    Of course, I&#8217;m not naive enough to think we can grow by adding drive shelves indefinitely (just added another one last Friday&#8230;).  My personal opinion is that we&#8217;ll ultimately move to an HSM system, especially since much of the storage is used for instrument data (mass spec, microscopy, etc.) that is often difficult for researchers to categorize immediately as to its value.  The thought is to let the HSM algorithms find the appropriate tier for the data automatically.</p>
<p>    A couple other points:</p>
<p>    &#8211; If you re-read the blog post, you&#8217;ll see that my main complaint with the 2020 was the lack of transparency with its limitations &#8211; and I know that I&#8217;m not alone in this department.  (Heck, I just got a private email in the past week from a disappointed new 2020 owner.)  Yeah, it&#8217;s low-end.  But working for a non-profit, without the sometimes cushy budgets of corporate IT, we&#8217;ll buy what we can afford and push it hard; our funding agencies expect no less.  Getting blindsided by limitations that we didn&#8217;t find out about during the sales process hurts.  Should we have done more due diligence?  Maybe, but the fact that we&#8217;re not alone in being unhappy with the 2020 suggests there&#8217;s a problem on the vendor side too.</p>
<p>    &#8211; I think you&#8217;d do well to pay attention to the Sun/NetApp lawsuit.  We use both NetApp and ZFS here, and I&#8217;m concerned that whichever side loses, it&#8217;s going to have an impact on our operations.  I also think the lawsuit may have important implications for the storage industry as a whole.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

