What I don't understand is on their flagship product, an all SSD drive array, they claim 500,000 IOPS (sustained I/O rate), yet i have heard of many people doing more than 1 million IP's/s in http and in database. If others can do a million how are they if something that is seemingly as fast as can be with an all SSD system can only do half that at a pure I/O level no less.
RAM caching.
How Doomed is NetApp?
71–74 of 74 posts
Re: How Doomed is NetApp?
#72Re: How Doomed is NetApp?
#73As a former NetApp person this makes me sad. I really respect Robin's opinions and have been following Storage Mojo for years. That Brian Pawlowski left to join Pure[1] is perhaps the saddest thing. During my tenure there he was pretty much the heart and soul of engineering. That he left to join a company that is succeeding with a product that he was tasked with building back at NetApp [2] boggles my mind. Connecting…
I respect Robin's opinions, but these days I don't think his finger is as firmly on the pulse of the industry as it once was.
Re: How Doomed is NetApp?
#74Earlier quoted context omitted.
Yes they do have snap manager but backups mostly keep failing. With exchange 2010 you have database, mailbox, and item level redundancy and protection so I don't actually see the value. S
HA != backup you can have whatever redundancy you want, and maybe even lagged copies, but if you need to restore something months older, you still need backups..
Exchange does not needs NetApp HA capabilities if you use multiple copies of database.
In our case NetApp sold snap manager for 30 remote copies of already triple redundant (one remote copy) database and then tape backup at month end.
In my view they just fooled the unsuspecting customer and just oversold everything.
That was fine too if it would have worked.