The most valuable features to us are the automatic failover, the peer persistence, and that ability to be able to be confident that if we have a data center outage, that our business will keep running. Those were the features from a business perspective that were the most important to me.
Improvements to My Organization:
Some of the benefits that we're facing in using 3PAR, I did mention before, are around the ability to patch our systems quite easily. We can easily failover. We know that if there are any issues, we can continue to provide services. We recently had a power outage in Aukland, which tested our data centers, our mechanicals, and electricals in the data centers. It also helped us understand that if we did have a problem in one data center, we could easily file between the two very easily.
The stability of the system has been great. I think we've only had it since October. We had not had any problems. It's been great, at the moment.
It's working for us on scalability, I think. We're still to see how we go. We've got some issues at the moment on scalability. We need to grow our data quite significantly. We need to find something that is more scalable.
The technical support has been absolutely fantastic. The whole project, when it went in, was really a joint partnership between HP, VMware, and the University. Everyone worked really well to make sure it got in on time, on budget, and was successful. It was a good project.
We knew we needed to invest in a new solution because we had a lot of issues in our data centers. We needed to increase our resilience and make sure that we could have our teaching and learning and research continue while we might have data center outages or if there was any problems.
The whole project seemed straightforward to me, as I was the business owner. I didn't see a lot of the technical issues going on in the background. It might have been a bit more complex for my team, but it was fairly straight forward. They managed to migrate 650 VMs without any outages. It was a Greenfields's solution. We didn't have any resilience for a number of our faculty machines. We had quite a number of data center outages because of some physical issues in the data centers. It was highlighted that not having resilience for our faculties, for their file services, and for their research, and for their cost material was not appropriate. We really needed to be able to put something in place so we could increase our resilience. It's also helped us to increase our security and all sorts of other aspects, and have all sorts of other benefits, not just resilience.
Other Solutions Considered:
It needed to fit into our current infrastructure. We needed to make sure that whatever we put in place had as minimal effort required regarding staff work load. We wanted to make sure that it didn't need any manual intervention in order to failover. The peer persistence that the 3PAR has was also important to us to make sure that we had replicated data, and we could access it quickly and easily. Recovering quickly and little data loss were the most important things to us. We had a few vendors on our short list. The reason we chose HP was it fitted those criteria very well. I would rate the 3PAR system fairly highly because it met our requirements of what we needed at the time. We're quite comfortable using it. We're seeing less stress from teams around issues that we have had in the past.
It just depends on what your requirements are. You've got to match your requirements to the system you need. Very important, we do reference checks. We do make sure we get all our requirements. We do comparisons. We've got pretty strict procurement requirements and we stick to those.
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Sep 20 2015