Please share with the community what you think needs improvement with HPE Nimble Storage dHCI.
What are its weaknesses? What would you like to see changed in a future version?
Nimble It's only available using iSCSI — Nimble can run iSCSI or Fiber Channel. Although iSCSI is cheaper, from a performance perspective, if you've got a really high-performance need, then you need Fiber Channel. Not to get too technical, but people tend to think that adding more ports gives you that much more bandwidth — that's not true. Every stream must be dedicated to a port. You could actually do port saturation and not use some of your ports that you just dedicated to your storage. It's not as mature as Fiber Channel — no one is. Fiber Channel is more expensive, but if high-performance is what you seek, then you need Fiber Channel. I hope that they bring that forward. They're doing all kinds of leaps and bounds with the new Nimble. I really love where they're going, but I think Fiber Channel should be on the docket for dHCI. It would be nice if they just provided a simple, easy to read matrix (white paper) on the different models. Today, it's a little convoluted. It's a little hard to read. You have to actually show it to a customer and explain it to them. I shouldn't have to explain it to them. It should be very simple: here are your options, here's your expansion, here's how much storage you get with that, etc. The information is kind of there, but it's just, it's ugly. I don't mean to call anyone's baby ugly, but they need to improve that datasheet. That would be my pet peeve with them. Their documentation needs to be simpler to read yet more detailed so it's easy to compare models and easier for clients to pick. They shouldn't have to have us sit down with them and explain to them why. They should be able to look at this and say, "Oh, okay. I understand where I need to be. I don't need a decoder to figure it out." That and the fiber channel are my pet peeves. The documentation needs to be improved — the quick specs are just horrible. I think there could be more automation capabilities; however, I think they're moving in this direction. More automation to open and close tickets, to get those service tickets open. They've done a lot in that area and I think that they again should focus on introducing more somewhere down the road.
They should include integration to the cloud like S3 bucket or the archiving part. The vehicle would be the backup solution. It would allow us to move some older, rarely used data to cloud.
I would like to see more compatibility with other vendors.
How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
Hi community members,
What are some important factors to keep in mind and to compare when choosing between HCI solutions?