Determining host-to-switch-to-storage mappings and keeping a running inventory of what you intend to connect to your storage will save you HOURS.. and HOURS and HOURS (Getting the point yet) of troubleshooting. You need to know as much detail as possible so when you bring in your storage you can besure it is all qualified.

SANS are like symphanies. If everyone plays nice things will sing.

If they don’t..

Well, I’m sure you’ve heard a violin squeek before.

:wq!ben

I find HDS Storage very reliable and the support received very responsive. As with any SAN environment, the main consideration is initial planning. Ensuring your Host OS and failover software, Switches and switch firmware level, and storage code level are all qualified. That would be the same regardless if you use HDS, IBM, EMC, or any other vendor. If you are looking at the Tagmastore, then you are looking for enterprise class storage and the ability to have active/active host multipathing. Additionally, the Tagmastore USP class allows you to perform virtualization and use the Tagmastore as a front end for external storage. i.e. if you have a netapp and you want to attach it to the tagmastore to utilize the throughput and multi-port config/etc. I could give you technical details but then I’d start sounding like a salesman.

In my opinion as someone whos worked with SANs for years, the most important consideration is your support model. The storage and all the bells and whistels the sales folks will mention is great and all, but when it breaks (which they all will) or you need a code upgrade, or the ability to troubleshoot why your host os lost connectivity to storage or you cannot see luns, or you have a fabric down, then your support with your HW vendor is critical. I find that HDS support tends to be willing to help me get out of a jam even if the problem is not related to HDS storage. Anyway, I could ramble, so post back if you have any more questions or would like to know something specific.

:wq!ben