The initial setup for NetApp OnCommand Insight is simple. I can install the tool on any other servers if there's a prerequisite and if you go to the interoperability matrix, you'll just need to stick to that. Once you install it, you can get it done on a single server, so it doesn't require any number of servers, compared to ViPR SRM where my company has thousands of servers in the backend to support that particular tool. I can install NetApp OnCommand Insight on a single server and get the environment up and running very quickly, so as your environment grows, you can just increase the resources in that particular server, and even if it has a lot of features, you can add the tags into the devices. If you want to do reporting, you can also use the tool or use OnCommand Report.

When we first went to Cluster Mode, we had a lot of problems. Setup took a few months. We had people onsite, including one of the top guys from NetApp for a while. Going from 7-Mode to Cluster Mode was rough. However, the last couple of upgrades to Cluster Mode have been fine.

The newest release was a lot easier, especially now that they're talking about their upgrades being more frequent. The whole non-disruptive upgrades can be scary because they are not 100 percent guaranteed. While it's always a little scary doing all non-disruptive upgrades, they have worked out well.

We upgraded the OCI and that wasn't complex, it was so simple. 

I was involved in the initial setup. I did the proof of concept.

It beats HPE products hands down in terms of initial setup. We were able to bring the OnCommand up in three hours, whereas it took 60 hours to bring the HPE solution up. So, it was a pretty hands down win for NetApp.

I was involved in the initial setup.

OCI, three and a half years ago was in its infancy, or for us it was. According to the guys who built it, they had a lot of problems at the beginning. There were a lot of templates that we needed within OCI that we didn't get. When we would go into OCI, we weren't seeing a lot of the data that we needed to see. It went on and on and on. They sent the same technician out every time and he just didn't seem to quite grasp what we needed.

About a year ago, they sent another technician out. He sat down with us. We drew out everything we wanted. Bada-bing bada-boom, literally within just a few hours he had all the templates impemented.

But a lot of it, as he said, was because it's a lot easier now to implement OCI than it was back then. Back then it was a lot more hands-on, command line stuff. Now, it's a drag and drop type of deal. If I want to see the IOPS on a server I can drag it over, drop it, and then it works. Whereas before, you had to build a template out for some of the stuff.

Our initial experience with OCI wasn't good. But, we stayed with it. Eventually it became something we use every day. We love it, we absolutely love it.

The initial setup is complex. There is a lot of stuff to set up. I had to teach my guys a lot of things, so there was a lot of learning. Once they got the hang of it, they were good to go and all the training that NetApp and the reseller provided was on point.

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

It was very simple, they gave us preparation for the user IDs and the like and we were able to put that in and it came in, right through. It took some time to come up with the data, the initial data and that was it, it was done.

I wasn't involved in the initial setup.

In terms of upgrades, when I was doing it a long time ago, it was straightforward.

Fairly straightforward, but after that, it's very complex to use and to learn and understand.

It was complex, and that's why we brought in Professional Services to get it up and running for us.

The product is very involved. There are a number of different modules so it takes a little bit of a learning curve to get up to speed on it.

I think it was pretty straightforward. I think it was very quick to pull in data sources from all the different things that we monitor. I don't remember having any hiccups or trouble getting all the data in and getting it set up.

I was involved in the initial setup. It was fairly complex. Due to what this tool is capable of, I think that is expected.

The initial setup is pretty involved - typically, the customer needs to go through a pretty lengthy process of installing SQL servers and about two to three different servers to be able to substantiate even in a small environment.

It was complex. It's new for us so there are a lot of requirements that we haven't had yet in other products, especially all these servers that we need to set for this application to run. That is not something that we usually do.

We need to prepare our environment for this product.

I felt like it was complex. They said it was simple but, they have a guy who will come out and help you through the process. He gave me a slight tutorial. Like I said, the data warehouse side is a lot more complex. So it had more of a learning curve, versus the performance side, which is pretty straightforward once you learn everything.

Regarding upgrades, the first one was complex, I think because we didn't have a lot of space on the server. But the backup wasn't working, so they wanted to back it up and then you restore from the backup to the new version. But the last one we did was very easy. So it's getting better.

I was not involved in the initial setup. We also have not upgraded yet.

Very straightforward. You need only to define how many collectors and enable the needed firewall rules.

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

I was not involved.

I was involved in the initial setup. It was straightforward, except for a firewall issue.

I was not involved in the initial setup of this product specifically, but now I'm involved in migrating from our current version to the new release that is available, which will help us to resolve the issues we've experienced.

I wasn't involved in the initial setup.

The initial setup was good.

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

The older products were medium-complex to set up but the new products are easy to set up.

I was not part of the initial setup or deployment.

I was involved in the initial setup. It was a little complex because we put it in quite some time ago. It's gotten a lot less complex. Overall, this is a complex package, at least in terms of it's capabilities. That is why it's not free. It has a lot of customization that you can do, such as reporting things.

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

It was very easy. No problems.