It's an adjunct storage repository and it compliments our 3PAR solution. We currently use it as a file store for backup, file, and compute storage workloads.
It's an adjunct storage repository and it compliments our 3PAR solution. We currently use it as a file store for backup, file, and compute storage workloads.
As an adjunct to our 3PAR platform, which is currently at capacity, it assists us in delaying the renewal of our 3PAR. It's an additional service on top of our storage solutions.
Something I would like to see is more clarity regarding the positioning of Nimble versus 3PAR. I am struggling with the boundaries within which these two are competing.
I can't comment on scalability just yet. I've just bought three of them, and I've got another five on order, but I am architecting it on a scale set at the moment.
I had capacity issues, and my scale-out of existing solutions was not viable, so I had to look for something new. I was forced into a Nimble purchase through an acquisition that we made, so I became familiar with the product and then decided to expand the product.
I use it as a rudimentary backup, so it's not the most effective use for the hybrid storage solution that we bought. I have bought an All-Flash for some virtual workloads, and that was quite a cost-effective solution for us.
I think good evaluation criteria include checking the scalability of the product. I also think the reporting aspect of it is very complete.
I would rate it at eight out of 10, and the reason for that is it's not as flexible a storage solution as the current versions of 3PAR.