And all that NAS
by Michael Hay on September 10, 2009
So we just announced HNAS 3080 and 3090 augmenting Hitachi’s portfolio. Note, I’m not going to belabor the technical merits, or the design approaches, or the value adds like the Hitachi Data Discovery Suite. Here is what I want to relate; It is rewarding to see dreams become a reality and I’ve discussed in the past this is a shared dream with BlueArc which started at the genesis of the partnership. I’ll pull a bit from my past post to reference Shmuel’s perspective on the partnership between Hitachi and BlueArc:
“The relationship between the companies is a true partnership. BlueArc is more than a technology provider or just a NAS component provider to Hitachi. Together we have improved our product offerings and embarked on a roadmap to deliver value through tighter integration.”
In essence Shmuel and I document and map out our companies’ futures, sometimes together, on the proverbial backs of napkins. This announcement is another proof point in our commitment of matching our dreams to our many customers’ dreams. A sincere congratulations to all involved in making this release happen!
Comments (3 )
In Praise of Partnerships « Technically Speaking… on 13 Sep 2009 at 5:08 pm
[...] http://blogs.hds.com/technomusings/2009/09/and-all-that-nas.html [...]
Biju Krishnan on 01 Oct 2009 at 11:20 am
Michael,
I have 2 technical questions on these products - very simple and direct ones.
Assume I have a 4 node HNAS 3090.
1. What will happen to the iSCSI connections if I bring down one node.
2. Can one HNAS node be on a different firmware than others, just for a short while.
Michael Hay on 02 Oct 2009 at 2:29 pm
Biju
(1) HNAS will fail the EVS containing the iSCSI target LUN to another node. This logically means that the TCP connection will time out and the connection will have to be reestablished. This can be coupled with things like tuning the timeouts on the initiator side, etc. to make the transition between nodes smoother from the initiator side.
(2) I think that you are getting the point, namely that in the case of a platform wide upgrade in the cluster’s Software inconsistent firmware versions are allowed, until all nodes have a consistent version.
