Anything new can be complex. There were some things in the initial deployment that I was not happy about. One of my directives was, "However, it's configured, ensure that it can never be overprovisioned." That one key thing was overlooked.

This is why I had to have a support call last year, because it actually became overprovisioned and I had to move some stuff around. We're still sort of in that with the Nearline storage, and that's why I'm having another architect work with me next week, so we can redo some things. I've had to move a lot of what was on the Nearline storage over to the LeftHand SANs. If I hadn't had those LeftHand SANs just sitting there with 20 terabytes, I would've been in serious trouble. That was my one point with the deployment team, everybody thinks, "If you do this, you do this, and do this, you'll never get overprovisioned," but I've been doing this long enough, and going back to Compaq StorageWorks, if you're not careful on how you have Remote Copy groups, your redundancy setup, thin provision, thick provision, lazy zero, and eager zero, then you will get overprovisioned at some point. You will lock up on a SAN tighter than a drum.

The initial installation is complicated. The storage administrator needs to be trained or they need to have a contract with someone who can take control over the system. Mainly in Denmark, the customers prefer someone to take control of the system. There are companies that will take care of their systems.

The solution is not easy to set up. It takes many weeks to set up. We need to enter some parameters before we set up the solution. Also, before we put the solution into production, it needs to be tested for almost two months.

The setup of HPE 3PAR StoreServ is not simple. The configuration is not an easy task to complete. The full deployment took approximately one month. We set up parts to implement, such as databases, applications, and hardware.

The initial setup was straightforward. The seller came and installed it, setting it up. We had just enough money. It wasn't that big of a deal to start creating LUNs at that point.

The solution is easy to deploy. The deployment takes a reasonable amount of time. We need one architect to deploy the tool. It is easy for one person to maintain the tool.

The very first 3PAR we got was an eight-node V800, so we were very involved because it was a very big five-rack system, a very large system. It was one of the largest in the southeast. The initial 3PAR was not very straightforward, we had to have help. But since then, we've been able to do some of our own installations without much trouble.

I was not involved in the setup of the original 3PARs we have, but I was involved in five subsequent installations. They were straightforward compared to other storage products that I've used, such EMC.

The installation is not that difficult nowadays. It takes approximately two days.

The initial setup is really smooth. 

The initial setup was pretty straightforward. It was easy to go back and look at it. It wasn't too complex at all.

We first started with the 3PAR V400 series, which is two racks that had to be wired together to provide 600TB of storage.  With the 15TB SSD based arrays we replace 6 racks of V400's with 8U of 8450's. 

The setup is complex. I don't think it's something that we could take on ourselves. I'm not sure if HPE does the same thing now, but when we bought it, HPE was actually the one that did all of the deployment. They did the "birth" right through deployment. You have to update the firmware, you have to update all the drives, you have to update the controllers. It's a pretty complex platform. In fact, I don't even think they allow you to do it. I think when you buy it, they do it.

I think it's complex enough. Hopefully, some of the tools that they are deploying now will simplify that process. But for us, when we buy maintenance, we also buy the support for them to do it. Even though it was complex, it didn't really make a difference to us because we weren't the ones doing it.

From set up to burn-in it was probably about a week. A couple of days to get it up and running, but then they had to upgrade all the firmware, upgrade all the drives. Then they had to do the validation.

The configuration is difficult but we had help from HPE 3PAR StoreServ. The whole process of the implementation took approximately one week.

If you have never set up a 3PAR, it can be daunting. There are a lot nerd knobs. There are a lot of things that we can turn on and adjust. It is easy to get lost in 3PAR. This is where our organization gives a lot of our time, in the setup. 

A lot of times people play with buttons just because they are there. That is where you can get in a little trouble with 3PAR. This is because there is plenty of stuff to do. That is where we try to get ahead of the game, and help them with planning and architecture, e.g., here is what we will do and here is what we will set up and do, because you can get yourself into trouble playing with everything.

We have a pretty good routine down now where the last two arrays that I did were all-flash 8450s, including racking time, and it took less than probably a handful of hours before we were up and running. We did about eight shelves. It is not overly complicated. It is more the OS and configuration which take more time. Usually, most installs never go beyond a day. The rest of it is just fine tuning and adjusting to the environment, depending on the size of the array.

The initial setup was pretty straightforward. The only complexity we've really had for the initial setup was actually with HPE, in scheduling. We have to have an HPE person on site to put the 3PAR in so they can vet it and all that stuff. Getting him coordinated, it was a wreck. The first time.

It is straightforward. I power on 3PAR and take care of the cabling. 3PAR is managed by two components: a services processor and a server component. The server can be a virtual appliance or a physical appliance. 

For upgrading, I take different configurations from the services processor. I update a package on the servers, which makes it easy to upgrade in production. For initial configuration, I do an upgrade offline, and it is easy.

Setup was pretty straightforward. We attended a week-long training with HPE onsite. Other than that, we've been able to manage it ourselves, for the most part. If there are any issues, we just call them in to support and work over the phone with them.

I believe they did most of the install in one day. They came out for two days or three days, but the majority of it was done - the initial racking - in one day; maybe some finalizations on the second day. It didn't take long.

The initial setup is very straightforward and simple. We also use Primera and PowerStore and the setup is pretty much the same for all of those. 

How long it takes will be determined by the capacity and the formats. It can take anywhere from six or seven hours up to 24.

We might need two to three staff members to handle deployment and maintenance It depends on the SLA and the organizational structure. 

It was not complex.

Both. The v400 was a complex setup where the 7400 was much more straightforward. The v400 had many requirements for how cables were run, specific hole sizes and cuts in the raised floor tiles, and the installation guide that the HP Field Technicians used was either out of date or incorrect in several places causing installation to take longer than it should have. In contrast, the 7400 had none of the requirements, as it was mounted in a more traditional style rack and the installation process was more mature. The service processor could now be deployed as a VMWare appliance and set up by the customer ahead of time.

The implementation was done by our partner and it took less than a day to complete. It was deployed within approximately five hours.

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.

The initial setup was pretty straightforward.

It was the easiest SAN that I have ever set up.

The initial setup was pretty straightforward. The guys knew what they're doing and I have a technical team to assist as well.

I rate the tool's deployment a five out of ten. It was completed in a few days. You need one resource to handle the deployment. 

The initial setup for this solution is indeed straightforward, although HP will not allow non-HP engineers to do the initial setup.

I was not involved in the initial setup. When I came onboard, the product was already in the environment. 

My involvement is primarily in the initial design of the system. I'm not involved with the actual setup. I will engage vendors recommended by HPE, or HPE-authorized vendors, to do the setup for me.

The solution’s initial setup is straightforward.

The solution's initial setup process is easy. If there are no hardware issues during initial configuration checks, the process takes two and a half hours to complete. It requires two executives for maintenance.

The initial setup was very easy.

The initial setup was complex because we didn't have experience with it. 

The initial setup was a little complex. It was our first time setting it up but now as we're doing another iteration it is much smoother.

The initial setup was pretty complex. There were a lot of different things that had to happen which was the reason why they had to send out the HPE engineers to help us. 

My philosophy is if you have to send out an engineer to do it, then it is probably more complicated for the end user.

The initial setup was not that complex. We work with HPE to take care of all the implementations. It took less than one day.

It was a bit complex in the wiring of the cages. Other than that, it was pretty straightforward.

Its initial setup was done by our partner, who has previous experience. So, it was relatively easy. 

The initial setup is straightforward with the help of the technicians from the company.

The deployment was completed in one week.

I was not involved in the initial setup. We did have HPE onsite to help with that. It didn't take too long, maybe two to three days.

This is a question better answered by the guys who actually support it, but it's my understanding that the upgrade process is pretty seamless. They scheduled it over a weekend, they rolled the upgrade through, and it works pretty well. Occasionally, there are glitches they need to work through but, from what I have observed, they're minor.

The process doesn't drag on. It's just planning, scheduling it, change tickets go in, and then they run it. It's a process that pretty much takes under a day. And then, after implementing, it's a matter of watching it to make sure everything is smooth after the upgrade finishes.

It is quite straightforward, it is a completely different architecture as 3par is licensed based on the number of drives and after a point it’s capped, i.e. you only pay for the drives and support.

I rate the ease of setup an eight out of ten. The deployment took three to four months.

The initial setup was complex.

I would suggest that you don't install it on your own, and you get help from an HPE solution provider or an architect to assist you with that.

The time it takes for the installation depends on the number of enclosures. However, the average time is approximately six hours. The most time-consuming part is doing the scaling.

The initial setup is straightforward. The moment that you are ordering a product, you pay for your support. When they come, there is communication going on between you and them. They check what is available for you. They send a person over, and that's it. After that, once the engineer has left, you have a working product.

It was so easy. When you make a volume, it takes seconds instead of minutes, if not tens of minutes. It took me less than an hour to set up the array.

3PAR installation was an easy one. We had really good consulting services that came in and walked us through that process. We've done a couple of field upgrades and those have gone smoothly also, so 9/10.

The entire setup, from rack and stack, to configuring the array, was shockingly expeditious.

It took longer to rezone my fibre switches than it did to get the Common Provisioning Group (CPG) configured and begin storage with vMotion VMs.

I was partially involved in the initial setup. It was complex because of our environment. We have 10 or 15 different systems in the background so it wasn't easy. We thought it would be easy, but in the end it was quite complex.

I'd like to be able to license different tiers of disks for different features. We have arrays that we could use for different purposes really. And so if I'm using near line drives for camera backup, I don't want to have to license them for things like dynamic optimization that I'm not using them for. If they're in the machine, now you have to license everything. So I'd like to see that. It might make things more expensive but I do like the model that Pure uses where it's just everything's included.

The initial setup is straightforward.

The deployment took about two weeks to complete.

I was involved in the initial setup but we did have Professional Services come in and set it up because we didn't have any training at the time. The setup was a while ago, but it took longer to unbox it because our reseller messed up and sold us all the individual boxes for every single drive. So the implementation guy wasn't very happy: four pallets of itty bitty boxes for every single hard drive. But soup to nuts, with that problem in play, the setup took about a week. If he didn't have all that, it probably could have been done in a day.

Overall the setup is very straightforward. It's just like any other enterprise storage. If you set up one you've set them all up, as it were. They're the same idea, different architecture.

The initial setup was complex. I would say it was flawed because we had issues.

3PAR is more complex to set up and start than EMC. There are a lot more things that you have to do and know that you need to do. Where with EMC, stuff sits there and runs.

The initial setup only took a few weeks to get it going. However, this is when we found out there were a lot of things that we did not have set up right. We just got these fixed about six months ago.

It took me a day to totally get everything in my mind regarding what we need to do and to teach my staff how to use it.

It was straightforward, comparatively easier than EVA. We had an HPE support person helping us throughout.

I was involved with initial setup. HPE came on site for the configuration and they were really good.

The setup was fairly straightforward, once given the proper documentation and we had knowledgeable people onsite. Our initial HPE people that we had out to help show us best practices and usage were ridiculous. The HPE person we had out that did the physical installation, unboxing, racking, and initialization of the array was good.

As long as you check the start-up manual, you should be able to deploy it pretty simply.

It was very easy.

The biggest part with 3PAR is overcoming your pre-existing mindset. So coming into it originally, the whole idea of chunklets and not having dedicated storage groups or, you know, raid types, it took time to understand operationally what what you could really do with it. And so in that sense, I would say that there was some complexity. From a services standpoint, they came in, they knocked it out, they got it installed, and we integrated into the environment. We started migrating.

They've made advancements in migrations, that, you know, I've seen now. It would have made life easier for us back then, but they've listened and they've, you know, made improvements.

Very straightforward. It plays with our Oracle products very well too, which we like.

It is very straight forward. Any person with basic storage knowledge can do the installation, with no specific training required.

I've been using it for so many years that, for me, the implementation process is quite easy.

Although I don't recall the details of the initial setup, I think that it was a little complex. The people that normally work with storage had to ask for help.

The initial setup was complex, due to calculating the amount of performance that we needed for the floor.

Earlier, it used to be complex. Now, we have our own skill set, which has made the installation easier. From the time we gather all the necessary data, it takes about a week (five business days) to set it up and have it running.

Initial setup was straightforward and fairly easy. The hard part was that we were on EMC VNX and trying to get those converted over into the HPE 3PAR, that process took awhile, along with scheduling downtime to get some of the physical stuff migrated over to the new device.

I wasn't involved in the initial setup but it was straightforward. It took about two days.

The setup is one of the drawbacks of 3PAR system, it's a fairly complicated piece of hardware. You need to get the engineers in to do it. So it wasn't something that we could do on our own. The Professional Services that we engaged with were wonderful, and it was a couple of days as opposed to a week or two weeks.

I think storage implementation is never so straightforward, but I would say it's among the simplest to implement.

I was involved in the setup and it was straightforward.

I was involved in the scoping of the solution. We were able to consolidate down from some of the old arrays very easily. In terms of implementation, I can only defer to the amount of time that it took, because it only took a couple days after the issue.

There's been some cases where we have migrated systems from one data center into our data center, and done consolidations. Some of that requires backing up older platforms, older systems, and bringing them in. We had one scenario where we migrated a customer, and they were using old LTO tape drives, coming into a new system which didn't support that. In those kind of cases, we had to reach out to HPE for support. Those were things we could handle. Again, during those migrations, I can't say that there was anything that we missed our window. Everything worked out very well.

The initial setup is straightforward if it is a single server. If there are multiple servers, the initial setup becomes complex.

The tool's deployment is straightforward due to experience. Initially, it was difficult. 

I didn't handle the initial setup or the configuration. I can't speak to how the setup went, however, it was my understanding that it was a bit complex.

There was two or three technical personnel that were used to handle the initial setup. They were admins and engineers.

Setting up 3PAR is somewhat complicated, and it took about a week. We need about two or three people for maintenance. 

I was not part of the initial setup.

The initial setup was complex only that we had never seen the solution before. There were some decisions that we didn’t understand the implications of in the beginning that we were able to redesign as the years of owning it allowed us to better understand what were being offered and how we could better utilize it.

The initial setup was pretty straightforward. It took a couple of days.

The initial setup was very straightforward, very easy to do. It took a couple of hours. It wasn't very hard. We only had about seven servers that we had to connect to the three chassis, so it was very easy.

I was involved in the initial setup and it was very straightforward, specifically for the way that we wanted to configure it. It was the ease of administration, setting up the pool, connecting it to the chassis and then, zoning it to our brocade fabric that made the setup straightforward.

The initial setup of the 3PAR environments, I would say is very straightforward, when it comes to a new technology. Not so much now, because we have five 3PARs in play. But when our first 3PAR arrived, we spent a month trying to break it, and we do that with any new technology that we're not comfortable with and not yet confident in terms of our own use of the product. And so getting that implemented and trying to break it for a month, you know, we couldn't break it, and so that was good. But that's kind of our model.

The initial setup process is simple and straightforward. The HPE team handled most of it, but we take care of the day-to-day monitoring. If I test an issue and communicate with their team, they provide online support. If we need physical hardware, they provide the physical hardware. 

The initial setup was quite straightforward. We didn't need any complex preparation or changing a lot of things in our environment to integrated it. It was quite straightforward. Bringing books and bringing it into the lab in a few days, then everything was migrated. It was very easy.

Initial setup was straightforward. It is not a hard array to set up and install. Even though we had purchased installation, this was back when we had the previous 3PAR for a performance tool. I got it and set it up.

The setup is becoming more straightforward now. Initially, we had hiccups during the upgrades and they caused some outages in our environment.

Now, the upgrades are doable at the customer level. They're point-and-click. They have brought the administrative functions down to the user level.

Usually, any 3PAR solution we offer includes the startup services from HPE. It is straightforward to set up. Setup is usually a same-day project.

It was straightforward.

I was involved in the initial setup and it was complex. There is more to it than there was in previous arrays, but I think that really ties into making the machine valuable to us. We probably have to rely on HPE a little more for the setup, but they did such a great job. I understand that it was necessary and I appreciate it.

It was very easy to set up.

The initial setup went easily as HP gave us training before we started the setup and use of 3PAR. This was a great experience, as we were working hand in hand with HP technicians on the initial setup, first run, etc. We gained a lot of experience and knowledge from them which enables us to go further with this product.

The initial setup is not overly difficult or complex. it's pretty simple and straightforward. 

The deployment is fast and within a day you can have everything up and running. 

We have engineers available that can assist with deployment and maintenance. 

The setup was straightforward. It was easy. Most of the activities were done remotely. The field engineer did a lot of it. The factory people get in and set up all the equipment.

The initial setup was complex. We had the HPE consultants in to work with us, and we had a few issues initially. But we managed to get them resolved.

It wasn't the most straightforward setup. It would be better with an easier setup.

Any time you're setting up a parallel file system, the setup is going to be complex. I'd say it was no more complex than any other. However, HP's limited experience with parallel file systems on their hardware (especially at the time we purchased the 10800 three years ago) was limited so a lot of performance tuning had to be done prior to releasing the system into production.

The initial setup was straightforward as it was planned for. Also, the installation document that was filled out had all the info required to make it that way.

Initial setup was performed with a reseller, but you should have some idea about how you would like to ‘shape’ your environment. All can be altered afterwards if you would reconsider.

The initial setup is complex, it requires you to do your volumes, fibre channel volume from the switch and the same connection from the storage. You also need to make sure you've created warning profiles. I don't recall how long the primary setup took, but the secondary one took us four to six hours to get it going. We used a consultant and we have 1,200 users.
We have about six people involved in maintenance, they are admins.

The initial setup is easy.

It was a little complicated to set up originally, as it takes quite a bit of rack space and we are a small organization. Once it was set up, it was well worth the effort.

The first array that they sent us was in some type of a factory mode. We didn't find that out until we loaded a bunch of data onto it, then we had to back it all off. We had to replace the array, which was sort of painful.

The initial setup was straightforward. It is quick and very intuitive. You can turn it on and figure out pretty much what you need to do right away. You don't have to have too much hand-holding for it. So, it's fairly easy to use.

It was straightforward, simple, and easy to set up, along with the OneView tools, for managing both compute and storage. It took a couple of days to set up, and two to three days to get familiar with the interface.

From a technical perspective, I'm not directly involved. I'm mainly from a management and overall overview of the system.

The initial setup was average.

It's definitely on the easier side when it comes to storage arrays. It's definitely a smooth array. It was smooth to get up. Smooth to expand.

The installation, which included migration from our old system, took approximately one week.

I haven't done the initial setup yet, and I haven't gone through the initial setup on the new one.

The initial setup was straightforward.

I was involved in the initial setup. It was pretty straightforward.

I don't do this sort of leg work, the keyboard stuff, because I'm an executive responsible for other matters. However, I have a technical background, so I know quite a lot about it. The feedback I received was that it went very well. Otherwise, I wouldn't recommend it.

We switched from a really old legacy platform storage solution. I'm pretty sure we were running it on NetApp at the time.

The solution is easy to deploy.

The initial setup takes about two days.

My team was involved in the initial setup and I managed the team. We had three resources that were a part of the setup, so they were onsite with the engineers. They got a week or so of training each. That was pretty much all we were a part of during the initial setup.

It was probably complicated because most of our team were used to EMC and it's a different kind of mindset. Even today, there are a lot of things that we haven't leveraged because we simply don't have the expertise. Over time, though, as we've used the tool, we've become more comfortable with it.

They sent us a team to work with us for the setup process. They still kind of managed the firmware and upgrades right now. It is pretty new and simple to use, it wasn't hard to figure it out. They sent one of their post-sales SEs to come in and go through the training. In two days, the team kind of got it. It's mostly that one of the goals to go back to a small team is we want something that is set and then to forget about it; we don't want to sit there all day and manage it. We want to put it on the floor, be able to do capacity planning, alert all those pieces but we don't want to manage it.

The setup was fairly straightforward because we emphasized simplicity as an important purchase criteria.

I was not involved in the initial setup.

Initial setup was very complex. These systems are very complex, but if you buy a converged system from HPE, the converged system is part of the package and HPE provides you with the technical expertise to come out and build the converged systems for you. They're built and tested at the manufacturing plant. You can go and visit the manufacturing plant and see them if you want. Some people can. Then they're sent to your site and HPE sends experts to build the 3PARs on site and assist you with the build.

It was a straightforward migration.

Very straightforward installation and set-up.

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.

The initial setup is easy. It takes between two to four hours to upload the functions.

The initial setup was straightforward, it took approximately 45 minutes.

The initial setup is complex because it needs a special engineer from HPE to take care of the setup and load balancing.

The initial setup was complex. It's not a straightforward integration. There are a lot of parameters that you need to configure, and each parameter affects a lot of other things. Even though we used a partner for the implementation, after the installation in the data center we needed to rebuild everything and reconfigure everything several times. At the beginning, it wasn't good. Now we are stable so, except for the performance issue, everything is working as we expect it to work.

The initial setup was pretty straightforward. We been setting up 3PARs for 10 years now. It is like second nature for us.

The straightforward setup also applies to experiences with Synergy and Flex Capacity.

The initial setup was straightforward.

I think once you know the system, the setup is pretty straightforward. Being somewhat unfamiliar with it going into it, it can appear complex. Once you understand the key concepts and the configuration points that 3PAR is using, I think it becomes easier.

We worked at it for at least two weeks, but we had other priorities than just setting it up. We were exploring, poking the box, so it wasn't just an out-of-the-box, get it set up process. The out-of-the-box, basic set up was about a day for rack and stack and then maybe another day or two - once we knew which configuration we needed on it - to have it fully implemented.

The initial setup, when we first got the gear, was actually done in coordination with HPE. They had installers on site. We didn't have that much to do. The next parts of the setup went very smoothly, integrating with Synergy.

It was pretty much straightforward, because our network is not that complex.

The initial setup was straightforward.

I wasn't involved in the initial setup.

I was not involved with the setup.

I think it is a complex setup. We didn't set it up ourselves. We had an HPE partner come in to set it up for us. Then we only dealt with the maintenance in running it. The hardware maintenance is done by HPE. Other than that, we do it ourselves now. I think that's fairly reasonable. Have somebody set it up professionally, explain to you how it should work, and then you can take it from there. That's the way it was in old-fashioned IT. This is transforming with all the cloud stuff that's going on, with all the automation. I think that's really getting to a different level going forward.

Of course it's complex, but with HP's help it made the setup easier.

As with most arrays, that is dependent on the system you’re installing. We tend to be “power users” and push the edges of how the equipment is used. In most situations, the setup is straightforward.

Straightforward from bringing the array on-site to plugging in and getting the first LAN provision was less than a day.

The installation is straightforward.

It was complex for us, but we were literally migrating nine data centers across the globe, from product A to product B. We got in our way more than anyone else did. I can't judge how the product would be in a typical environment, since we are talking about 75 petabytes over nine data centers. It was a big project. 

The product is straightforward enough. If we were to do it as a new implementation, it would not be an issue.

The initial setup was simple. It took me a single day to set it up.

The initial setup was straightforward and easy. We did the whole thing, including compute networking, like it was almost a a greenfield type of scenario. If we had not had an issue getting our circuits put into place, it would have been just a few months and we would have had the whole thing done. However, it was not just storage. It was a new virtual environment, we were putting in NSX networking, new networking switches from HPE, etc.

The initial setup was straightforward.

It is straightforward. It's user friendly.

When it comes to upgrades, if they're complex, they're complex from our side. We need to identify what we need exactly, and most of the time this is done with a consultant or in cooperation with HPE and their partners. Once we know exactly what we need and what we're missing, then it's straightforward.

The setup of the storage itself was OK and not too complex, but there are additional VMs (or appliances) needed for remote support, reporting, etc., which can only be set up by HPE or a partner technician.

The installation was actually pretty straightforward. Everything is well-documented, which is another big plus. HPE has always been there for us through each step.

The initial setup was complex. I was one of the first customers to get their StoreServ 7400. It wasn't a good experience at all. The guy who set it up didn't really understand the technology that he was building. He didn't have build documents. The solution that I was initially sold wasn't correct so the workloads failed. It was a nightmare.

The initial setup was straightforward. I don't think it was too complex. We've used other technology that's much more difficult to use. I haven't had 3PAR experience before, mostly Dell and Hitachi and some other EMC.

The initial setup was complex in that requirements were not communicated well through the VAR and some parts needed to be sent back (PDU’s were of the wrong type) and the VAR assumed a Virtual Storage manager would be used, but a physical manager was both requested and required, which created an installation delay while the correct equipment was shipped.

Straightforward. Wasn’t overly complex.

The initial setup of 3PAR was straightforward.

It's very straightforward to configure. You need to connect the service processor to the storage array and then finish the configuration settings.

The HP setup spreadsheet is a beast. It's much more extensive than any previous SAN, but going through the process addresses almost every issue that's likely to come up.

The installation of the solution required three people and took three days, but for the storage-side, it took eight hours to get running.

The initial setup was easy. However, we get stuck on preconditions. We were not aware of some of the preconditions. For example, the need for a different, separate IP network for replication. We had to rethink how we were going to implement it.

The setup was complex from the perspective of the employees having to go through five days of training. If they simplified the administrative process of maintaining the unit, that would go a long way.

HPE has always done the initial hardware setup of the solution. It is straightforward, because we have good local engineers.

We brought Oracle in to set it up. We didn't go through the entire setup process because Oracle was part of it. Oracle itself did it, so it was pretty easy for us. One good thing was that we didn't have to worry about the patching, OS levels, and other stuff. It was pretty easy for us.

The initial setup was very complex, because it was our first installation.

The setup was pretty straightforward.

The initial setup is rather straightforward.

The initial setup was fairly straightforward. We migrated since we are totally virtualized on VMware. We changed all the storage to the 3PAR within a few weeks. Without any downtime or anything. It was very, very good.

I was involved with the installation, but I didn’t do too much. We had HP EVA and we upgraded to 3PAR. It went smoothly. There was a lot of old data that had to be moved to the new tool, and there were no problems at all.

Initial setup is relatively complex.

We have teams that work with the fabric directly and do all the fiber channel setup.

The initial setup was a bit complex and took much longer than we anticipated. We have 5,000 users now, but it took us two years to be able to get there.

Setup was straightforward.

Initial setup is straightforward. The wizard guides you through the installation process, but I always install the 3PAR and SP via CLI to eliminate any deployment issues that may occur when using the wizard.

Setup was reasonably easy. We used a CD and a VM template to “birth” the unit. It was all wizard driven and intuitive.

It was straightforward. I was in the datacenter with one of the HPE engineers and we went through everything. He was knowledgeable, he retired about a week after he set it up. So he had a lot of experience.

It was not complex. It's pretty straightforward. It took approximately two and a half months, the project which we have run through it. So it's pretty good. And now that our actual deployment starts off, we'll get to know the actual time lines on it.

The setup was pretty straightforward.

I was involved in the initial setup, and it was very straightforward. The HPE engineer came on site, sat down, showed us how to do things as he built and designed it. It was very good.

Initial setup was relatively straightforward.

The setup was straightforward, without any kind of problems. We installed it very quickly.

We needed HP specialists to help stand up the 3PAR systems. It was a little tricky. After that, things were straightforward.

Initial setup was complex because we didn’t have any previous knowledge. It's been two years since, and I think it’s essentially a simple setup and we just didn’t have any prior experience.

Complex in initial pre-requirement and finding the serial numbers and the necessary information for setting up the system.

Pretty straightforward - even though HP says "self installable" I highly recommend a qualified person with a great deal of understanding of virtualization, zoning, etc. Could a person with no experience using storage do this? Eh...maybe getting the array on-line, but I would not recommend it (nor would I for any vendor).

The initial setup is very simple.

The installation and configuration are quick. You can complete them in one or two hours, which is fast.

The initial setup was complex, but we had the partner there to help.

The initial setup was straightforward; configured the management interface and it was ready to use. After the physical deployment - you need to connect the power and network - it should not take more than one day, even less than one day.

The initial setup was straight-forward. We came from the P9500, so it was more or less a rip and replace. It was involved with the project to replace our Blade infrastructure as well, but from start to finish, it probably took six months from design to implementation.

It is very straightforward. It is very simple.

The initial setup was straightforward.

Setup was very easy. I think even for the 8450 - we had also prepared ourselves -but in one day we had installed everything and it was up and running. So it's easy to set up.

The initial setup was fairly easy, but you have to understand it well if best practices are to be gained.

I was not involved in the installation. I wish I would have been involved. I inherited it.

The initial setup was quite straightforward. Of course, we had help from the HPE specialists, but it was straightforward.

Initial setup was straightforward.

I was involved in the installation. We have problems every time. Sometimes there are three parts to one problem.

For example, I had to get help from the engineering team in India. It took a year to solve this issue. There was new documentation in which the installation requirements for the disaster tolerant systems changed. That is one of the installation issues.

The initial setup with different tiers and adaptive optimizations was very easy after seeing the DQE. Migration of our data that first time was also very easy.

It was straightforward – it was stood up pretty easily and management is simple enough.

We don't really handle the setup. It's done at the factory and delivered. It comes with data sheets to help customers with a few things, however, for the most part, it is pre-setup to spec. Once it is delivered it can be configured as necessary.

The setup was straightforward, because of the partnership that we maintain with Logicalis. They supported us during the whole deployment.

It was very easy and straightforward to set up.

The setup and configuration were pretty straightforward. We were able to quickly adopt it and to get the ball rolling.

The initial setup was straightforward. 

The initial setup was not complex or difficult. It was pretty straightforward and easy.

The initial setup was straightforward and easy to setup. It can be done in a couple of days.

The setup was straightforward. It was not a complex implementation.

Initial setup was straightforward.

The setup was complex because we were using iSCSI and we don't have a lot of iSCSI at our shop; this made it a little bit more cumbersome for us since we're generally Fiber-attached. This was resolved after we contacted HPE support.

The initial setup was straightforward. HP’s business partner assisted with the installation and were able to get the 3PAR up and running in very short timelines.

The initial setup was simple.

I'm not working with 3PAR directly. I'm a manager. But from the experience of my employees, I don't see that they have any issues with complexity. To be honest, we have a senior administrator with a lot of experience with 3PAR and other vendors' storage, so I think it's not too complex for him.

The setup was complex, because the technology is new in Central America.

I was involved in the initial setup and it was really, really straightforward and easy. Because we are one of the biggest customers of HPE 3PAR solutions in Switzerland, our problem was that the consultants weren’t with us during the installation. The installation was just done by installation wizards.

When we did some auditing, we requested a highly technical guy from HPE to come directly to us. They sent us someone from another city and he did okay, given our large environment. For our environment, installation wizards are not so good. We needed to fine-tune the installation. For basic environments, for perhaps 70-90% of installations, the installation wizard should be okay.

For the most part straightforward. HP had an engineer available onsite for one week to help with setup and any questions that we had.

It's a straightforward setup.

Out of the box deployment is easy.

The initial setup was very easy. It went very quickly.

It was straightforward. No problems.

The initial setup was pretty straightforward.

It was very simple with a user guide provided from HP representative.

I wasn’t directly involved in the initial setup, but I think it was pretty straightforward.

We used HP best practice and we consulted HP. We got it right and it works well for us because of that.

HPE does the initial setup (hardware and initialization) which makes things much easier. Using 3PAR is simple and straightforward, unlike its competitors such as EMC.

It was straightforward as HP did most of the setup.

It depends on what aspects you need to configure.

The initial setup is easy. It is easier to install than Hitachi. You need two or three people for its deployment.

The initial setup was straightforward. 

No comment, because we requested our local vendor to perform the setup and configuration for us.

The initial setup was easy.