What is our primary use case?
Generally, clients use the solution as primary storage or data storage for corporations. They also use it for data replication where they replicate to another site or even on the same site. They're typically replicating the data for a backup situation.
How has it helped my organization?
The solution has greatly assisted data performance as far as a VM-ware environment goes. My data performance is much faster.
What is most valuable?
One of the features that I like the most is the data replication element. The reason I like it is due to the fact that it's pretty clean on replicating data over to a second site.
The product stands on its own in heavy enterprise environments.
It's easy to make changes without affecting the environment.
The solution is very easy to use.
The product is very robust and offers very good performance.
What needs improvement?
HP has several integration elements that work with other vendor storage products. I'd like to see a greater expansion on that so that a customer can do a more seamless migration from other vendor products. The migration of data to their platform could be better.
Primarily they don't have a lot. They have several EMC elements that they can migrate data from, however, there are many more controllers out there and it'd be good to see a more seamless integration so that that could occur.
I'd like to see 3PAR have some integration with Cloud services.
For how long have I used the solution?
I've been using the solution for several years. It's been probably around seven years or so. It has definitely been a while.
What do I think about the stability of the solution?
The stability is pretty decent. The only thing you have to worry about is that you don't overtax the controller. In other words, you don't do that combination of deduping and compression as well as data replication and then also heavily use the controllers where your IO starts, the IO performance. With IOPS and Truepoint, it's important that users do not over-utilize the environment. Then you have performance issues.
What do I think about the scalability of the solution?
You have to be careful about exactly what your usage is. You really need to understand what you want to do with the controller. You need to understand what your total IOP performances will be, before you do any sizing so that you can size appropriately, otherwise, as with any storage, you could have an underutilized controller. That would then cause you frustration and business units would suffer as you would have slower performance than what you expected.
A lot of times customers get themselves in trouble due to the fact that they make a purchase or size a controller and then later on they undersized it. Sometimes the under-sizing can occur due to the fact that a company starts putting more demand on the new stores where they want to put one more device on the storage product or connect to it, and that wasn't what it was sized for at the time. If you didn't plan on the growth of the utilization of the controllers the product doesn't look like it's performing properly, however, indeed it is. It's just, not big enough to handle the new user profile that you have put on it.
Microsoft Exchange, VMware, SQL, and Oracle - those are the types of software or devices that are applications that were used within our environment. We have several different departments or groups that get access to that storage.
Which solution did I use previously and why did I switch?
There were some older 3PARs that we wanted to replace and there were some Clariion EMC products that we wanted to replace. The reason why was due to the fact that the 3PARs, were four years old and we needed a technology revamp, so to speak.
The other reason we switched was that EMC was just too slow. It was getting overwhelmed and we had to go to a stronger or newer technology controller. Therefore we decided to go with the 3PAR as it was a lot easier to use. We also liked the virtualization of the product and we appreciated the ease of being able to make changes without having an overall effect in the environment.
How was the initial setup?
The initial setup is straightforward. It's not too complex. If you have any SAN experiences pretty easy, as you have to understand some of the terminologies so that you can pre-prep the architectural design that you're looking for. Overall, however, it's pretty easy from a GUI perspective. You can do everything from a GUI. You don't need to play at the CLI level. Of course, if you'd like to do that, you can do that as well.
What about the implementation team?
I typically handle implementations for my clients.
What other advice do I have?
I'm a consultant and an HPE partner and I have my hands on several different things in terms of products I use.
Normally I work with all the versions as far as software versions. I've worked with all the different hardware, 3PAR versions as well, and I do a lot of installations.
The big thing and with 3PAR and with any other storage - and this goes for any kind of storage as you're sizing - is to make sure that you are getting the right size environment for what you currently have and what you expect for future growth. Otherwise, you may run into performance issues.
On a scale from one to ten, I would rate it at a nine. We've been quite happy with the solution so far. It's robust and offers very good performance.
Which deployment model are you using for this solution?