I enjoy understanding how the setup works. I never have any issues with it. 

The previous guy set it up before me, and I've picked it up and run with it. I haven't really had any issues since then.

I do remote support, so I'm not working on the data center side. We have an on-site team that could better describe the installation and deployment. However, my impression is that deploying AFF is straightforward. 

The architect is the main person working with the NetApp products, and he does a deep dive before touching any product. Our team has minimal exposure to NetApp because our work involves a mix of vendors. We have people working on the NetApp side but not regularly. The architect spends a lot of time on NetApp in his day-to-day activities, and he makes the changes. He takes and gives recommendations about which product to use, whereas we provide remote support from a different region altogether. The implementation, changes, configuration, and decision-making are all done from the headquarters.

And once it is implemented, the remote team logs in and does the navigation part. We check the array and identify any problems. If we find anything, we immediately reach out to the architect. He's the one who engages with NetApp and relays information to the remote team. That's how we learn as an organization. We spend time on the products to gain knowledge and experience with vendors.

It is easy to deploy and use. It takes three to five hours. One person is enough for it.

The initial deployment was a bit complex. At the time of implementation, we created a parallel setup and gradually shifted from the old setup to the new setup.

I am a nerd at heart, so I worked with our professional services group to do the rack and stack. It was pretty straightforward. It was based on the idea of centralized controllers with expanded disk shares. We were able to work with our professional services consultant to get it set up in two days or so.

The initial setup was straightforward. 

We did a six-month proof of concept and put it through its paces. We had a cluster in our primary and backup data centers. We tested out SnapMirror Business Continuity quite thoroughly. That was a new technology for us, and it's still fairly new in its own right. We even did some automation in the proof of concept where we built out a process that explored what our refresh process would look like on NetApp. We were able to bang that out in about three days. It was easy. I was involved with that from day one.

The initial setup is complex. It should be easier.

The initial deployment took three days, and that was working on it two or three hours a day. We got two appliances, 2750s, at the end of last year and we completed the setup about three weeks ago. We set up the volumes and the v-servers. We are currently configuring the system and, in the next month or so, the appliance will be done and it will be transferred to the new site offshore.

Our deployment included initializing all the disks, doing the network configuration setup, including the IPs, the mask, the gateways, the DNS, et cetera. Then we had to apply the licenses for all the services. Next, we had to create the volume structure. Then we could start mounting them on other devices so that we can integrate the storage itself with the rest of our system.

We have five people working on the solution.

The initial setup has a moderate amount of difficulty. Dell PowerSTore is easier to set up. This is not difficult. However, it's not too complex. You just need to do more work in order to properly use the solution.

I cannot recall what the deployment process was, as it was a long time ago. The last time we did a deployment, it took two weeks. It was a special installation, and we have less storage capacity than expected, which caused issues. We had to install it twice. 

We only require minimal staff for deployment and maintenance. There isn't too much maintenance as you just configure it how you want and you leave it. Typically, the product is very reliable so it doesn't require attention.

The initial setup is straightforward. We connect to the external screen and enter the basic admin information before we can start the deployment.

The deployment of NetApp AFF was a bit complex, mainly due to the extensive functionality it offers. 

I was involved in the initial deployment of AFF. I've done it quite a few times and I find the process to be straightforward.

The deployment could be easier. Pure setup is way easier in comparison but I had no problem setting AFF up. 

The initial setup has a lot more steps in it than are probably necessary for a base deployment, unlike other vendors where it's more straightforward. It could be a little bit more streamlined.

I was not involved in the initial setup of the solution. 

The initial setup was straightforward. It took under an hour to set up.

The initial setup was pretty straightforward.

We found the setup straightforward. I've been using NetApp for a long time, though.

The initial setup is not very simple. As I always use the CLI for configuration, it is easy. But the nodes' and cluster configuration can also be done with GUI.

The solution is deployed by connecting everything in different locations and then implementing the solution that will be sold to customers. The deployment is done by three engineers, which include two senior engineers and myself.

The initial setup was straightforward.

The initial setup was quite straightforward, and we had an engineer who handled most of it. It was impressively easy and hassle-free.

Deployment time depends on the size of the organization. If you have engineers, the implementation can be done in-house. 

I've never deployed the solution. I've just worked with it directly. 

The initial setup and deployment of NetApp AFF is pretty straightforward. A lot of terms that were used in 7-Mode became easier and were more clearly stated when we transitioned to cluster ONTAP.

Our transition lasted a year or so. We had a lot of data to move. We used the 7-Mode transition tool. My entire team of six people was involved.

I was not a part of the initial setup.

I was involved with the initial deployment of the solution. The setup was complex on our end. Our internal processes are difficult as we have such an extensive environment. For example, we must go to security and do all the reviews and assessments. It's our internal program. There's nothing on NetApp.

The initial deployment of NetApp AFF is easy. We can deploy it in a very small amount of time. The NetApp is pre-configured so you just have to run the setup, with some workloads that are already ready. In a few hours you can have production running on it. And for customers, it's very easy to learn how to use it.

The implementation strategy for each environment is always a little different, but the main architecture is very similar. We always do a workshop with the customer, at the start of a project, and we design it for their specific requirements, but overall, the architecture is always similar.

We have a specific service for the maintenance of NetApp, and that team has six people, but they maintain all our NetApp installations, not only AFF.

The initial setup was straightforward. We have been doing it for a while, so we know how to put it together.

The initial setup was easy, similar to other NetApp FAS installations.

The initial setup of NetApp AFF is straightforward.

The initial setup was straightforward. Nothing to it. The professional services from NetApp came in to help us out, and they knew their stuff.

The solution was easy to deploy and took half a day to complete.

The deployment was done over the course of a couple of months. This was mostly scheduling time on our end to work with the integrator. We then had to schedule time to go prep it to be moved from Manhattan to New Jersey, before moving it, setting it up, and getting things back online. So, it took a couple of months to get set up.

For customers who had it moved or shipped directly to the device's final destination, it shouldn't take that long to set it up if you have either a quality integrator or a substantial amount of experience with NetApp. 

The initial setup was straightforward. We use a metric cluster in NetApp, so getting that set up initially is very complex. Once it's working, it's very simple to manage. But a reseller helped us install that. I don't think it could be any more straightforward. It's a necessary complexity.

The overall setup is very easy. Deploying a new cDOT system is the hardest part. On our business side, because our environment is very complex, there was some complexity that came up. In general, that is one nice thing about Netapp. Regardless of how simple or complex your environment is, it can fit all of those needs. Especially on the network side, it can fit into those environments to take advantage of all the technologies that we have in our data centers, so it's been really nice like that.

We could definitely spin something up pretty quickly. It takes about ten minutes which is pretty quick. We have a very good team that does that as well.

The initial setup was very straightforward. It was intuitive to set up storage volumes and get the networking functioning. Their engineer was very helpful. We got the current array on our production site the very same day it was shipped in. We had it up on the network and started to put some storage on it. 

The initial setup process is okay. If you are experienced, it is fine. 

While it's not easy, with the instructions they have, it's straightforward. It just takes some level of expertise or experience in NetApp solutions to be able to do it.

One of the biggest impacts that this solution has had is on time to deployment. It takes a lot less time to set up a new infrastructure for a company. Our hosting setup went from being a couple of days to a couple of hours.

The initial setup depends on the goggles that you have on. If you are an experienced technician, then it is relatively simple. However, for a customer who just bought it and wants to set it up themselves, then it might be a little bit hard to figure out.

My implementation strategy is always that when we sell systems that we do the implementation ourselves. This is so the customer gets a fresh, good experience with a fully updated system rather than a controller that has older systems. We rely highly on the customer's satisfaction, e.g., they see the project for what it is instead of what it could be.

On average, the deployment takes roughly one day, and that is running through everything. It takes one day to get it up and running, setting up the first SVMs, ensuring all the connectivity, etc. In most cases, the greatest hindrance in the entire setup is the network setup, which does not have anything to do with NetApp.

In our particular scenario, we had a failing. We had another vendor storage array that was failing. It was a Hitachi that was all spinning medium. When that went down, we reached out to NetApp. They were able to help us out with CDW to get us loaner equipment while we were purchasing the all flash.

There was a little bit of complexity there. However, once we got the all flash in, we were able to cluster it together with the loaner equipment and move everything over on the back end. There was no impact to VMware, and everything else was as smooth as could be.

The product's deployment is straightforward. 

NetApp AFF's deployment is easy. The tool's representatives were very helpful. 

The initial setup is straightforward. It is not a big, complex job.

We are in the process of setting up and transitioning to a Hybrid cloud environment, but it takes some time. We are currently exploring it. We have thousands of servers in AWS and Google cloud, and we have an internal VMware cloud as well.

We went from twenty-four 7-Mode filers to an eight-node cluster, so we've done a huge migration to cDOT. With the 7-Mode transition tool, it was a breeze.

The initial setup of the product was very straight forward to me. I'm certified on just about all the NetApp NCIE (NetApp Certified Implementation Engineer), all of those things like SAN, NAS, and Data Protection. So to me, it was very easy. I mean, they did a wonderful job helping set it up, but as more features are added it became more complex. Someone could easily forget to do one thing, like setting up a firewall, internal firewalls and stuff like that and leave some security holes. But it is fairly easy if you have some expertise and are a little careful.

The process was easy to consolidate into one AFF HA pair. It was simply doing volume copies and across SnapMirrors in the environment. It just migrated right over. It wasn't a problem at all.

The initial setup was very straightforward, but complex. With the new clustered environment, you have to have a virtual server instance to run anything through the cluster, so you have to create a B server and a data logical interface to use block, then you create a separate lift if you want it to use files. The virtual instances have to be in place before you can actually use the product.

As for the initial setup, we were on FAS initially, and the migration was not smooth because the 7-MTT tool was not that mature. After the initial hiccups, however, the experience has been okay, and we are pleased with this product.

Building a cluster was not complicated, but ONTAP was not stable. I remember one upgrade that lasted for more than 24 hours. It took the same amount of time with FabricPool, and FlexCache still has loopholes. It is not efficient. There is still quite a lot of room for NetApp to strengthen its ONTAP core.

We were migrating data from 7mode to Cdot, and it was a new build. Also, ONTAP testing was new, so we didn't have many benchmarks to work through. The migration and ONTAP testing were not smooth. We had quite a number of problems, and we were forced to do a lot of upgrades. The issues related to compatibility had to be escalated to the highest level of the NetApp engineering team and the product build team as well. We worked closely with them.

As for deployment, we had some issues with switching at the cluster backbone when building a cluster. Other than that, it took us less than a month or so because we had professional services as well. We were able to build the solution in 90 days.

The initial setup can be both straightforward and complex. It's like buying a big toolbox filled with a million different tools, and wrenches and spanners and screwdrivers, and things of that type. You could use that toolbox to install a doorknob or could you use it to build a house.

If you wish to use every tool in your big toolbox, it's a complex environment that requires sometimes more than one skill set.

The initial setup is not complex at all. It has been made easier compared to other vendors.

The initial setup was fairly straightforward, in that we were doing this migration from an old NetApp to a new one. However, because of the problems with latency they were having on that, it got a little bit complicated because we had to shuffle things around a lot.

The technical support helped us out well with these issues, and on the grand scheme of things, it was a very straightforward migration.

The initial setup was pretty smooth because NetApp came onsite with their support. They gave us the option to send a technician onsite to do the whole cabling. We were part of the architecting of the whole design, in terms of how we wanted to leverage our data lift and be able to leverage how we want to take control of the data. With their support and being able to set it up through the OnCommand System, it was not a lot of clicks. The initial setup was pretty straightforward. From the expectations that we had and the simplicity of setting it up, it wasn't so complex.

So far, we only have rolled it out in one of our data center heavily. We tested it out, and it's working well. We have put a lot of production workload into it. Our next target is to roll it out across all the data centers. We are hoping to save almost 30 to 40 percent of our footprint initially. That would be a big savings for us.

There were a few initial setups. Two of them were relatively straightforward and one of them was a little bit more complex, the AFF8080. On that one there were a lot more network interfaces to figure out where they go.

We also leveraged the IP Spaces which was really good because we house some data for an affiliate, rather than somebody in-house, so that was amazing.

Initial setup was straightforward. There is only a small amount of NFS and the rest of it is CIF, so setup is very simple.

The setup is pretty simple. You put an IP on the box, log into a web interface, and it basically sets itself up. It requires a bit of customization for your environment, but it prompts you, so it isn't difficult. It takes 10 to 20 minutes.

The solution's initial setup is straightforward.

I was in charge of the original setup. I worked with our vendor to help actually do the install and configuration. It went really well. Coming from a 7-mode background to a cDOT was definitely a lot different with the lists and similar items to configure. It was very straightforward. We pretty much got it on the network within something like 30 minutes; got our VMware environment pointed to it and within a couple of hours, we already had data on it in the first half of the day.

I was involved in the initial setup. It was straightforward, because we actually did an all-flash FAS before there was an All Flash FAS. We bought a FAS system with the SSD shelves and made it into an all-flash FAS before NetApp had an offering. Since that time we have bought additional NetApp All Flash storage and deployed AFF systems to various datacenters across the globe.

We've been installing fast-flash systems for 20 years, so I'm highly experienced with them. The complexity of the deployment depends on the customer's environment. Some storage systems from other competitors might be easier for the customers, but we are a service provider, so we do the installation and train the engineers. From the end customer's perspective, it doesn't matter if the system is easy or not because they don't need to install the system. 

We do the training, installation, and heavy lifting. The system is a bit more complicated to install compared to other competitors. We can offset this because we are highly trained and have all the experience required.

The initial setup was straightforward. It's always been very easy with how everything works, and their support has been pretty solid too.

The initial setup of this solution is straightforward.

The setup was pretty complex. There was a lot of compliance and there was a lot of security requirements, but it went pretty well.

It took us two to three days to set up and provision enterprise applications using AFF because we're a little different. We do short duration uses which means that we build everything from scratch, tear it down, and build it again. 

The setup was not complex, but we have good project management skills.

It is straightforward. The whole cluster configuration is pretty straightforward. Just bring up the node and add to the existing clusters. We didn't see any difficulties.

It takes us one day to set up and provision enterprise applications using this product. Migration takes a lot of time but provisioning is setting up the cluster and that takes one day.

I was involved in the initial setup and it was very straightforward.

Straightforward. No different to any old system that we've put in before, so an AFF is no different to a FAS.

Initial setup has been easier and easier because we used to set older systems up with SAS and aggregates and everything else. Now, it's kind of, start it up and let it go. It's getting a lot easier, at least on the hardware setup.

The initial setup is straightforward for the customer. We require more in-depth disk management and understand how the disk will be distributed. Otherwise, it is simple.

The implementation of NetApp with CIFS and NFS is quite quick to deploy. When they came out with the latest models, they provided us with three protocols. Going forward, this will be very useful.

It takes one to two days to deploy NetApp AFF. Apart from the basic configuration, there are many things that need to be done for the integration part, like antivirus integration, LAN configuration, and NDMP configuration. Those all take time. So it can be done in two days, but it might take more time depending on what needs to be done.

The initial setup was complex.

The move from older FAS systems with older disk shelves to the newer AFF A800 systems is a transition that is a nightmare in terms of rack space, moving data, and trying to do it online so that the customer doesn't experience downtime. It was a multi-day upgrade.

The initial setup is straightforward. It's not complex.

We have connected to AFF public clouds but I'm not really dealing with it.

It took us less than two minutes to set up and provision enterprise applications using AFF. 

Initial setup was straightforward. Installation is easy, but we spent a long time proving it's good; convincing our users, which are application developers or DBAs, to move to this one. But the initial setup is piece of cake.

Me and my team did the initial setup. Setup was more complicated than their 7-mode platforms, but it's a necessary evil to provide the new functionalities within CDOT and AFF.

It should be straightforward because we know it; it should be straightforward.

The initial setup is not complex.

When we changed to NetApp it took one to days to migrate everything.

NetApp does the initial setup when you buy the equipment.

I've set up a NetApp network previously. The setup was pretty straightforward.

It was pretty straightforward.

I was involved in the setup.

They preconfigured it at the factory and that is a pain in the neck. This should stop.

I was involved in the setup.

They preconfigured it at the factory and that is a pain in the neck. This should stop.

The initial setup of NetApp availability can be considered medium difficulty. If you have experience with NetApp systems, it is relatively easy to medium in complexity. However, if you have never installed such a system before, it can be quite challenging.

The initial setup isn't really completed. It's easy.

The initial setup was easy for us. The consultant was always there to support us. They have always been helpful in understanding the technical points, how it will help us going forward in terms of implementation, future scalability, and possible upgrade of storage components.

I never found it to be complicated, but I have a lot of experience with NetApp setups.

After upgrades, it's very intuitive and easy to pick up. 

I was involved and it was seamless. We had a two-node star cluster with AFAs on them. NetApp did the install. A few years ago, we used to do our installs ourselves, as a company. Then we started using NetApp installation services to do them. They did the install. They inserted it seamlessly into our cluster. It came up, we had the arrays, and we could create aggregates on it, pretty much right after they got them installed.

I was partially involved in the setup. It followed the same setup process for any other FAS system. It is pretty slick. The setup is pretty decent.

I know it uses the same OS, so I don't see why it would be different than any other FAS system. It has a different flavor, but it is not completely different. It is not using an “out-of-the-blue” OS.

It's a simple setup. What we spent our implementation time on was getting the fiber channel LUNs presented to the host; that went really well. The problem is, we need to configure it in Wisconsin and then we shipped it across an ocean and had some non-IT people install it into a rack and turn it on. That was the complexity. We all added it ourselves. With that said, because it was a simple, one-shelf system, they were able to get through it and get it done. There was one cable that wasn't connected right. Support helped me track that down, and then I had them go plug it in right. They turned the connector upside down and then it worked; what a shock...

For this install overall, for NetApp's part, it was simple; we have the complexity.

Initial setup was done through me in combination with professional services. We had them do the racking and cabling through a VAR that we use, but then we specifically had joined it to the cluster and configured it.

Initial setup was pretty straightforward. We were able to leverage some of the documentation on the NetApp site and get through it in under a week so.

Initial setup was easy. We had one small system. We have a lot of FAS systems; we have a single AFF right now. It's an 8080, with just one shelf. It was a very simple setup. We're familiar with cluster mode already.

Rack it and call it good.

The initial setup was straightforward.

We filled out a spreadsheet ahead of time that contained everything necessary to get us going. When it came time for the deployment we went with the information on the spreadsheet and deployed it successfully.

The initial setup was straightforward. We've been deploying NetApps for the last 15 years. We are pretty familiar with the boxes.

I've been using the technology for years. For every model and version, the deployment is basically the same.

The initial setup for AFF was very quick and almost painless. We had professional services come in, they put it together and before we knew, we were carving all our discs, all our LUNs, and migrating data. Of course, the data migration was also really fast for us. We used to have older infrastructure. A little less than a year ago, we got brand new infrastructure that's all flash and we migrated it less than a year ago. It was no pain whatsoever.

The initial setup was not complex. Even though it's a higher performing platform, you run it, manage it, and administer it the same as you do any FAS.

The initial setup was complex. The fact that it has to interact with both IBMs - AIX - and with the Epic application, means there are three vendors in the mix.

I work on the phase when the solution when it is being designed. My involvement would be more on solution designing. Once the solution is finalized and has gone through, the implementation is not that difficult of a task.

The initial setup is very simple. System Manager 3.0 is built into it, which makes it easier to set up the system. It probably takes about 15 to 30 minutes.

I was involved in the technical and commercial analysis, but not in the actual environment setup. That was taken care of by another team. The initial setup was straightforward but there was definitely a lot of planning that went into getting it deployed smoothly.

Being a services provider, every customer has unique requirements, which makes it more complex for us. We took a good amount of time to understand, evaluate, and come up with a proper deployment plan so we wouldn't get into trouble at the deployment phase.

Initial setup is pretty straightforward. Especially hardware-wise, it's not much different than what we currently have; we're pretty used to installing.

I was involved with the initial setup. It was fairly easy; a little bit different from a traditional FAS but very well managed by NetApp as the install engineers.

Initial setup was very easy; it took maybe 30 minutes to do.

NetApp AFF's deployment is straightforward. You can deploy it within half a day. 

The initial setup is easy and straightforward; there is no complexity.

We have clusters but our guy doesn't know how to do the cluster side of things. That's what the reseller did, primarily.

The initial setup is straightforward. It is GUI-assisted. There are a lot of step-by-step guides, which are easy for certified engineers to follow. That makes things simple and we are able to make a good impression on our customers.

I was involved in the initial setup. We have an AFF and a FAS. We were able to set those up in a cluster.

It was very straightforward.

The initial setup was straightforward. There were no problems. We usually have a professional service engineer in the data center, and we have certified engineers within our organization to work together to design and implement.

Initial setup is a little bit complex, but we use a guy who pretty much builds all of our NetApp for us.

Initial setup was straightforward, but it was because we used professional services, to have somebody come in and let us drive as they guided us. The console is pretty basic, but the professional services answered all of our questions, which made it easier for us.

Installation was fairly simple.

In terms of the initial setup, you need to know what you're doing with it. That's another reason why I'm going over to Pure. It's much simpler.

In simple terms, you just rack the hardware, you load your codes, and it's ready for configuration. That is pretty straightforward.

There was not much complexity involved. Since this was a new setup, migrations were not in order. So, it was pretty straightforward.

I would say the initial setup was straightforward. When the stuff ships out, it comes with diagrams of how everything needs to be wired. The online resources are great to read through and the ONTAP system is consistent across platforms. Deploying AFF is less complicated than deploying older solutions.

Pretty straightforward.

Given the advanced disk partitioning and ONTAP 8.3, that was a small learning curve, but that's not unique to flash. Actually, it was pretty simple to set up. The fact that we have a heterogeneous disk type in the array made it simple. Our choice of aggregate type was very simple. Basically, we split the unit, an 8060. We split the capacity across both heads. It was pretty much a vanilla roll out.

My role in the initial setup was only plugging it in, basically. It's pretty straightforward, especially with the fancy little map you get with the hardware. It was pretty easy.

In small ways. For the AFF, I was involved in the initial setup but not directly doing a whole lot of it. I consulted, and we set up the aggregates and all that based on specifications. It was straightforward and, again, we had good providers; good help makes things easy.

Cluster mode setup was complex to do the first time, but everything else was straightforward.

The tool's deployment is easy. 

I installed NetApp for many, many years. The initial setup of NetApp is very simplistic. Even as an installer, for years upon years, there's a giant poster board that I still use to this day, because that tells me exactly where my cables are supposed to go. It just gets me off the ground quickly and then it's just a matter of following the GUI and knowing what you're doing.

Since we already had it running on a fast system, we just added them to the cluster and moved the data, without the customers even knowing. Just seamless.

I was involved in the initial setup. It was very straightforward. By the end of the process, we had it down to where we were converting an entire park within 48 hours.

I was involved in the initial setup. It was very straightforward. By the end of the process, we had it down to where we were converting an entire park within 48 hours.

Initial setup is not too bad. The cluster system I did not too long ago; you just console cable into it. It's got a guided setup on the CLI. After that's complete, you're on the network. You can use your web browser and access the OnCommand Manager application and start configuring SVMs and all that stuff. It's not super difficult. I know there are products out there that are probably easier. I've heard that Nimble Storage is supposed to be one that's really easy to use. On a scale of 1 to 10 in terms of complexity and everything, I'd say NetApp stuff is probably about 7 for me. I've only been in SAN storage and everything for, like I’ve mentioned, about three years. I'm still relatively new to the industry of SAN storage. I'd give it about a 7.

Initial setup was straightforward.

Initial setup seemed pretty straightforward. The vendor pretty much took care of most of it, but it was more of the implementation of the VMware. That's what we were working on, or what I was working on, anyway. It was fairly simple.

The initial setup was straightforward. It was just like any other FAS system. Just install and enable some features for the AFF systems. It was not like a regular FAS system, but other than that, configuration is exactly same; simple and easy.

We used professional services from another vendor for the initial setup, so we didn't feel it was that difficult.

The training for AFF was not difficult; it wasn't complicated.

Initial setup was good. It's quicker, now that they've started sending out the pre-configured systems, or optimized systems.

Initial setup was pretty easy. I think it only took maybe half a day to do everything; put it in, power it, connect all the cables, configure it. I think we put it in production within like half a day; not difficult.

Initial setup is generally straightforward, but NetApp has good technical articles and guidance on moving from one NetApp controller to another NetApp controller. It was pretty straightforward for the most part.

Setting up cluster-mode, initially, close to two years ago, was a little bit difficult, but after I started using it and after I went for NetApp training, I now feel it's easier than 7-mode.

It was mildly complex. At the time, I had very little experience with seven-mode, and we had some falste starts with getting cdot configured. But we used the seven-mode migration tool for 20 terrabytes of data in two days.

Setup was simple and easy.

It was very straightforward on the setup.

The upgrade was actually very easy too. We didn't even really need to do a traditional migration when we did our "migration" to it. We didn't have to do the setup by migration tool. It was easier to set up the new cluster next to the old one, and then set up intercluster links and SnapMirror all the data over, and then just bring that volume. We did a planned failover, like we would for a disaster recovery, where you just bring up the new system, bring down the old system; that's how we did it.

Actually, we took that old system to make our disaster recovery, so we just sent that to our failover site and then we already had the data in sync too. We didn't have to do that whole process of syncing the data across the LAN, we were able to do it right next to each other on our LAN, so it was super fast, and then sent over our system, and then just resume the SnapMirrors.

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

I was involved in the initial setup. It was somewhat complex, because we did cutover from 7-mode, where we stood up a brand new platform, were having to move the data from one to the other, and were dealing with the outages that were involved, but also going from the seven-mode to the ONTAP and the clustering and how it is different.

I also do a lot of the infrastructure, as far as the fabric management, the ports, the trunks, and the fiber-connections from the NetApp platform or the NetApp cluster to the IBM Brocade Branded Directors. I do all of it: the zoning and the fabric management. It's very detailed and very complex. You have to really know what you're doing in order to get that set up properly. It is not on NetApp. That's just in general. If it was any system, you would have that to deal with.

Initial setup was pretty straightforward. We went to a boot camp prior to doing the install. We had a pretty good understanding of how it all worked, so the implementation was pretty easy.

Initial setup was both straightforward and complex. We used their tool that provides a no-file-copy copy. The goal was to switch all of our existing shelves to our totally new heads. It was sold as being fairly painless, no-change process. In practice, there were a fair number of changes, a fair number of tweaks, but that's from a purely time perspective. The amount of time it would have taken us to actually copy the data was nothing compared to the hour of downtime that we actually had to do the head shelf. From that perspective, from a user’s perspective, everything paid off quite well. From the admin side, there was a little bit more work than just turning off a switch and flipping a switch.

Initial setup was just racking and stacking, basically; that was about it. Rack and stack is very straightforward; we had help from technical support to cable it. From that point on, it was pretty easy.

The initial setup was straightforward and easy, but we had a few problems implementing the devices due to a lack of training and the fact that it was a very urgent implementation.

It's a straightforward and easy setup. It was guided and we had the documents to install it. It took around two days of racking, stacking, and installation.

The initial setup of this solution is straightforward, at least for me. I've deployed NetApp before in my previous jobs, and it was easy with my experience. That said, it is not very complex.

The initial setup was straightforward. I'm very familiar with NetApp, so it's more of the same. I didn't have any problems.

I'm generally not involved in initial setup. Usually where I get involved is after it's gone through RDS, and I do the automation orchestration as far as our customers' provisioning and billing, etc.

We had Pro Services, but we were heavily involved.

For someone who is experience with any NetApp platform it's very, very straightforward, very similar to anything else that you would do. Obviously there are some specific guides, specific to AFF. You want to make sure you're following those best practices, but other than that it's a cinch. It's something that I could have done on my own without Professional Services, that's how easy it was.

I'm only involved in upgrades. They're pretty simple, and their documentation is very clear, and it's all really nice.

Initial setup is complex, in that you have to make sure that you're setting it up in compliance with the best practices. The best practices are well documented. There's not a lot of, "Oh my gosh, I didn't see that coming", kind of thing. You just have to make sure you set it up right; otherwise, you didn't get what you paid for.

I was involved with the initial setup; did the whole thing. We build it, from the time they ship it. Once they get it to us, I take care of everything; networks, the whole nine yards. It’s straightforward. It's very easy, but of course we've been doing this for years, so it could be complex and we wouldn't care.

NetApp All Flash FAS:

I was involved in the initial setup, which was very smooth, very easy.

Pure Storage M20:

Initial setup was very straightforward. You plug in a management port, you plug in your iSCSI, your NFS or your fiber channel ports, and you're up and running.

All-Flash FAS:

I already had some prior knowledge of the spinning FAS systems. Compared to those, this was much easier. It took us something like three hours to set it all up. It was really fast.

EMC VMAX 10K:

I was not involved in setting up the VMAX. I just have to deal with it.

Deployment was really very easy because we were somehow experienced with moving the system into other data centers. We went into a similar exercise about the end of last year where we moved into different areas of the data centers and have been running two data centers. We used Data Guard for Oracle workloads so the downtime was very low because we simply had to switch over during migration. The skill set was already there in the company. We almost did not need any system administrator. They provided the amounts for running NFS.

It's a straightforward Next > Next > Finish setup, like Windows.

NetApp is very easy to set up.

All of the solutions by different vendors have setup wizards but with NetApp, it walks you through the steps and it is easy. It has NAS, CIFS, NFS, and block, all at once. Building the lines and going through is done step-by-step. With other vendors like EMC, you have to get a separate filer. There are a lot more questions that have to be asked on the front end.

NetApp also talks seamlessly with VMware, and most people are on VMware.  

It was really straightforward, for the most part. We were used to working with FAS already and this is just adding All Flash and SSD to the mix. It's a lot of the same standards we had already.

The initial setup is very easy.

Implementation was not easy.

I've actually shadowed a NetApp consultant and it looked to be straightforward. I can't wait to do my own in the future.

It was pretty straightforward. Our need and setup for it wasn't crazy.

Not straightforward, there is a learning curve when it comes to AFFs, but once you understand the setup it's pretty easy.

We normally set up our clusters ourselves. We request professional services from NetApp when we want to add new machines into the cluster. But for other tasks, such as to configure, generate reports, create the aggregates and move databases across the cluster, we don't need technical support. It’s relatively simple.

If you can set up any FAS, you can probably set up a AFF. Initial setup is pretty simple, if you know that technology.

The thing that I love the most about it is, being a NetApp customer for a while, they code their cabling; you know where the square plugs in, and you have a triangle and a circle. That makes it so much easier; they idiot-proofed it, very much. Then, of course, when you go through the setup and configuration, it alerts you if there's any cabling issue, so you can go back; that was kind of nice, too.

It's very easy. We've been using NetApp products for five years so its just another NetApp system for us.

I think we took about two weeks to get up and running. We performed initial tests and diagnostic tests, all the results of which surpassed our expectations. We were able to get 400,000 IOPS from our system processor.

The initial setup was really easy. It took three days to set up once we got it.

The cloud setup is easier to implement. The on-premises setup is a little more complex.

We deployed it a few weeks ago. It took one to two weeks for planning and two weeks for final implementation, but it can take longer if there is any kind of migration or change of product.

In terms of complexity, the initial setup is somewhere in the middle. It is not straightforward where you can run it out of the box. You have to set it up and configure the network. 

It's always a little bit complex when you're trying to integrate a new piece of hardware, with cluster mode as well. There's always a learning curve, but with that curve, there is knowledge which stays with me for the life of that technology. So, that learning curve is essential.

We were migrating from Data ONTAP 7-Mode to its Cluster-Mode. Therefore, we had to get swing gear, then do the migration from loner gear and back onto our new gear. This was a bit difficult. It took us several months to do multiple migrations. Fortunately now, we are on Cluster-Mode and don't have to do that again.

It was a little complex. There were a few changes that we were not privy to. For instance, they had the 40 gig converged NIC that we didn't even know was available until we got it. Learning how to adjust that and manage that was a little bit different, it was a little bit of a learning curve, but it was not horrible at all.

I am the lead for all NetApp installs. Every time we had a good installer coming onsite, so we make it easy for them and they make it easy for us.

Initial setup was very simple, very straightforward. We knew exactly what to do, so it was easy.

I wasn’t involved in the initial setup, but I think the team found it fairly straightforward. We had good support from NetApp. We worked very closely with our account team. They walked us through very well and we had no issues getting going, as far as I know.

A lot of what we've been doing is migrating from 7-mode. We have run into some pain points. I don't know that it's necessarily NetApp's fault. A lot of it is just our inexperience. Some things we hadn't really thought of; moving the LIFs, that sort of thing. We've had some major network storms that we weren't expecting. Had we read deep enough into the documents, I think we would've found that before we tried it.

In the pre-CDOT era, upgrades were a nightmare. Replacing a node was not an easy thing to do and getting downtime was not an easy thing to do. After CDOT, I'm hoping we won't be running into that situation.

Initial setup it was straightforward. Because we're so used to the FAS systems already, it was easy to add the All Flash FAS system; it was so much easier to deploy.

I was not involved in the initial setup.

A cluster mode setup is quite complex, generally speaking, and quite involved; not as intuitive as I would like it to be. A one-click install would be nice, something where you can just have a GUI-driven system where you put in the IPs you want to use and the interfaces you want to install them on and call it good.

We're very knowledgable with NetApp, is the initial setup was very straightforward. If you're anew customer, the whole system comes complete pre-configured, so that's very, very simple. If you buy the pieces separately, then you have to configure it yourself, and if you're not knowledgable with NetApp, it's going to take some time to complete.

It only took one day for the initial setup of a normal system, including performance and system monitoring. So setup is quite fast and straightforward.

It was straightforward.

Its initial setup is easy. The deployment took a few days.

The initial setup was straightforward. They had all the codes with them, they just implemented them on the system and, next thing we knew, it was up and running.

We did the initial setup. I would say it was an eight out of 10. There were some issues but it was okay. They helped us fix it, and we figured it out. That's mostly because we just like to do it ourselves, because we want to see what we're doing and what's in our datacenter.

It was reasonably straightforward. We received a lot of knowledge on the net about ONTAP systems, so the setup has improved.

We had a vendor help us, but it seemed like it was pretty straightforward.

I was involved in the initial setup and it was straightforward.

From my experience with NetApp products, initial setup is going to be nice and easy. We are very techy, so it was easy for us.

The initial setup was generally straightforward, though there were a couple areas that could be streamlined or made a little more clear in terms of which direction we should go.

The initial setup was very straightforward. When you've worked with NetApp for a while, it is very easy to setup their new systems. If you are new to the system, then there is a learning curve, but NetApp provides great documentation.

The initial setup was a little complex, because we weren't very knowledgeable in the NetApp at the time. We were using a third-party, and they didn't have a lot of technical individuals, so it took a while to get it out.

Initial setup was very straightforward, with the new optimized arrays that you can purchase and they come in with a 10-minute setup. That did take away a lot of the steps that we used to do before. So, it did come in, we were able to just plug it in and in 10 minutes have it up and running.

Well we were a 7-mode shop and we were switching to CDOT. There's a little bit of a transition there. I won't say it's overly complicated; it's just some new things to get used to.

The setup complexity is why I have not given it a perfect rating; not that it's a big deal. We had professional services come and help us do that but going from 7-mode to CDOT was quite a jump.

I have a feeling that’s pretty common. We were going through the conversion on all of our arrays. We currently have three. It's getting easier as we go through the process more and I understand it. It would be a lot better if the transition was a lot more smoother.

I set it up the first time myself. I needed to learn it and read the user guide for it, but it’s easy for technical people.

The initial setup wasn't easy, and in fact took about 6 years. It was a slow start, but of course it was new back then, and it takes time.

It was very straightforward. There are setup tools so if you're not very familiar with NetApp, they walk you through the process step by step: How to configure all the interfaces and the SVMs, etc. I'm more experienced with the command lines, so I deployed it that way. But it's very receptive to PowerShell scripting, so it's easy to use.

I was involved in the initial setup. There was a little bit of an issue, but it turned out okay. Basically, we had to call NetApp for assistance during the setup due to an odd issue.

The installation was pretty easy. It was my third setup, so it was nothing really new. There's only one minor switch that turns it into an AFF.

Initial setup was easy.

We used their professional services. They came in an installed it for us and it went really well; flawless. They just went in and took care of it all. Then we just put our configurations in and away we went. I thought it went pretty slick.

To get my certification to build it, I found it a little bit grueling. Everything is tailored to our specific organization, following the documentation. It's different documentation than what NetApp uses. I’m not familiar with the NetApp filer documentation.

Initial setup was pretty straightforward, the same as any other FAS solution, except for when you get into the disk slicing and other features for setting up your root aggregates. It’s pretty standard configuration, pretty easy. That has been our experience.

Initial setup was very straightforward, just simple. It wasn't difficult at all.

The networking is extremely complex. They advertise it as pretty simple but you have to get through a big install phase before it becomes simple. That's my impression.
To prepare for that install phase and make it a little less complex, make sure your NetApp partner knows what they're doing, by talking to people.

It was straightforward. We did greenfield. We went to two new data centers so the installation of it was pretty straightforward.

Our initial setup involved a lot of development. It was complex mainly because we had to make it simple. We had to simplify it for our own customers, so it was complex for us but it's a very easy solution for enterprises.

It was very straightforward.

Very straightforward. NetApp already does all the installation for us. They just come in and set the IPs, etc.

If you are new to NetApp, it is a bit complex, but if you know the system, it is quite simple. There is definitely a learning curve, but every NetApp system works the same, so if you know NetApp, it’s quite easy.

initial setup maust be done by cli, storage space privisioning made by gui, good interaction with vmware with vsc 

I was involved in building it. I found it a little bit grueling to get my certification to build it, but I really can't speak to the NetApp filer documentation. The documentation that we use for it is different from what NetApp uses.

I was involved in the initial set up. It was very straightforward. Working with our partner, they tend to do a lot of the work on our behalf but it's still a pretty straightforward process. That were really no gotchas.

NetApp's initial setup is very straightforward. It's very easy to get up and running within a day, as long as you have the cabling in place and the power, but that's outside of NetApp's control. Once you have that infrastructure in place and they come on site, it's very easy to get up and running within a day.

Once you’ve done one, it seems very intuitive. However, the first time seems very complicated.

We do the initial setup ourselves. We use the CLI, so we don't use the simplified methods because we have some special requirements most of the time. 

Initially, the setup was complex because it was new and very different, it was 7-Mode to cDot. We got a lot of support from NetApp so it wasn't an issue. It was just complex, but they provided the assistance we needed.

For me, it was the actual installation onto our company's hardware. There are several instances that came down to the unknown. The NetApp engineers, as well as my engineers, could not necessarily predict the installation difficulties. Once we overcame those, and started creating application notes for both our company, as well as NetApp's company, I believe it will help others down the road. It could help the software engineers to program different options into the installation.

I was not involved in the initial setup, just basically the attainment of the technology for our teams, for them to deploy it.

It was an easy setup. It was done very quickly.

Initial setup was complex. In spite of the new CDOT 9, NetApp setup is still complex. It requires configuration of all the network interfaces, SVMs, which can become a little overwhelming.

The reason the initial setup was straightforward is because we've got clustered Data ONTAP on their hybrid system, so we know how to do the installation on our own.

It is very simple, let’s say, any person who has never even worked with storage can perform a load to the server very easily.

We actually had a partner assist us in setting it up, but it seemed pretty easy. It's a lot different with a cluster and IPs; you have to think about things differently. Other than that, it seemed pretty easy.

It wasn't complex.

It took one week for the startup to pepare the storage for use. We have migrated about 150TB of data in six months (VMware, Oracle, SAP, filesystem, etc.).

The initial setup was just fine and straightforward.

The initial setup is very simple. How much time it takes depends on the size and what the initial setup should be. It can be a long process.

It's easy. If you know NetApp, it’s actually easier than 7-Mode.

I wasn't involved, but those who were told me it was easy.

The initial setup was straightforward.

The initial setup was straight-forward with the exception of the ADP aggregate setup and spare drive management.