The stability of this solution has been great. A couple of interruptions that we had were not really related to the product. They were more related to Azure, where we had a couple of issues with actual Azure hosts which run the virtual storage device and Cloud Volumes ONTAP.

The performance is top-notch. We've never had anything go down. If it does go down, it will be back up within minutes. 

The solution is not stable when using single nodes. This is a problem. NetApp should work on this solution to make it more stable with HA nodes and resolve this issue.

We've had no issues.

CVO is highly stable, and the performance has met our expectations. It does exactly what it needs to do.

I would rate NetApp Cloud Volumes ONTAP's stability at eight out of ten. 

The stability is pretty good. There was an instance though where we were trying to delete a CVO instance off of it, and it took me a while to get it to release. It took a while to delete one of the instances since we already had taken it out, and it was asking to delete it. It couldn't connect to it to delete it. We ended up trading a new workspace and then deleting the old workspace.

We've experienced a few minor issues with stability, but we haven't encountered any significant outages.

Its ability to detect ransomware or external threats has been highly effective. While we haven't experienced any actual ransomware attacks, we have encountered threats. These threats are promptly addressed by our vigilant security team before they can infiltrate our environment. The stability has significantly improved over time. In the past, there were challenges, but now it's much more reliable. It simplifies our workflow, eliminating the need to navigate through various steps on our desktop.

Cloud Volumes has been stable so far. We haven't had many issues. If there are any issues, it's typically during an upgrade. Some tools are upgraded automatically through the cloud manager, but it's nothing major, and the upgrade has been smooth as well.

We had issues with Azure when they did maintenance on the nodes. They just do their maintenance and it's up to us, the customer, to make sure that our applications are up and data is flowing. When Azure does their maintenance, they do maintenance on one node at a time. With the two nodes of the CVO, it can automatically fail over from one node to the node that is staying up. And when the first node comes back online, it will fail back to the first node. We have had issues with everything failing back 100 percent correctly.

We have had tickets open with NetApp to have them look into it and try and resolve it. They've made improvements in some ways, but it's still not 100 percent automated for everything to return back. That's an ongoing thing we have to keep an eye on.

It is stable, at least with respect to Azure, which is what we use.

There's always room for improvement. Overall, it's still stable.

NetApp is stable. 

As far as I know, everything is stable.

It's very stable. We haven't had any issues since setting it up. It all depends upon the disk. The faster it is, the better the performance.

It is a good system. It is very stable as far as what I've been using with it. I find that support from it is really good as well. It is something that I would offer to all of my customers.

Cloud Volumes ONTAP seems to be fairly stable so far. The only time we have issues is when there is a circuit interruption, but this product has been pretty stable. We haven't had issues with crashes or data getting corrupted. We've had interruptions due to internet problems or leaks between the sites. 

These are things we have no control over because they're different providers. That's the only issue that I've seen. But once those come through the actual system itself, it's been fine as far as resiliency, performance, and availability.

We haven't had issues with stability so far. 

So far, we have not had any issues. There were only a couple of panics or something like that, but those are normal issues you deal with once in a while. 

In all the time we've been running it we have had no issues. It's great.

I cannot comment on stability right now because we have not been using it in production as of now.

We are just validating the cloud for a couple of our clients, so we haven't had it affect our client storage operations.

The stability has been really good. I don't think we've ever had any major outages. AWS, obviously, doesn't guarantee 100 percent uptime, so I can see that it's not been up since I last restarted it. Rather, it's been up since some AWS event resulted in it migrating to another one of their pieces of hardware. But we've never had it actually crash.

It is stable compared to other storage solutions. 

It provides a stable storage for flexibility. Everything is perfect and works quickly.

We upgraded last month. I am not a fan of the upgrade to 9.7.

So far, it has been very stable. We haven't had any downtime or other stability issues.

The stability is very impressive and we have had no issues with it.

The stability is very good. We haven't had any outages.

So far, so good.

It is a stable solution. I rate it seven out of ten.

There has been just one incident since we started using it, in which a node refresh needed to be done. The stability is pretty good with only one incident in 14 months. We're pretty happy with that.

I haven't had a problem yet.

In terms of stability, this is a rock-solid solution.

So far, the product is as stable as anything else in the cloud. It's up to us to make sure if we need a high availability to put it in. Other than that, standard nodes allow for faster and easier deployments for lower critical environments. Stability-wise, the product has been fine.

It is highly stable.

It is very stable and versatile, but you need to have an advanced degree to administer or monitor it.

It's very stable. We've only had two outages with NetApp in seven years. One was a planned outage to fix a problem - that one was seven minutes long. The other was an unplanned failure, which caused us to be down for about five hours. Overall, we're still within our five- and six-nines of availability, so we're happy.

It is a stable product. I haven't had an issue with the stability of this product.

It's pretty reliable. It's an HA solution, so even if one cluster goes down, another cluster can support everything.

So far, we haven't had any downtime. 

The stability is perfect. We have had no problems. On-premises was also good, so I'm not worried about this.

It's very stable.

The stability has been very good. The only time that it was down was because someone took the machine down. That was in the beginning and then we fixed the permissions. But it wasn't an issue on NetApp's end that caused the system to go down.

ONTAP has been very stable for us, specifically in the cloud environment. It allows us to have high availability as well as standalone systems if that's what we want within our specific workloads. Also, on-premise has been a very stable environment. We have very few outages and when we do, we work with support to get systems back online in a timely manner.

I cannot precisely say what the SLA availability is for the platforms, but in general, the stability of the cloud service provider, whether you put it in AWS, Azure, or even in GCP is very good. There are very few moments during the year that those platforms have instability. Normally their availability is at "four-nine's."

The stability is only lacking when you have a problem with the underlying subsystem and the hardware has failed. I have not encountered that problem so far. 

When doing tests for some of our LOBs, I realized that if your aggregate goes offline then you would have to do a manual failover. That means if you are using CVO for instances, like VMs or, on the on-prem world if you are doing hybrid-cloud connectivity, then you would have to unmount your disks and mount them back. That would be a disruption. 

But when it comes to overall product stability, if you don't have any underlying issues, it works fine. But if you have a subsystem level issue, then you will have a problem.

The stability is good. I've been with NetApps for a long time, so I've seen them fall and come back. However, with cDOT and all this new stuff, it is great. It just works.

From my months' experience, I haven't seen a single point of failure within the ONTAP, except for Azure maintenance.

The stability is great. We have been doing different scenarios about errors from controllers, to disks, and so far it is very stable. We have not had any issues. We upgraded our own version and did not have any issues there, either.

The on-premise NetApp is very stable. I can't speak to the cloud side.

It just works. I don't have problems with it.

On a scale of one to ten, I would rate the stability a ten.

The stability has been great. We haven't had any issues.

Actualmente, no tenemos ningún problema al enfatizar la herramienta. Confiamos plenamente en la estructura de seguridad que gestiona esta plataforma multifuncional.

Stability is quite good. However, when it comes to bugs, this is where we are taking a hit. We have ended up in situation where new releases of the ONTAP create an issue in our current infrastructure. We either need to go back or find a solution to fix the bug created by the bug. This is the issue that we face now.

We are not putting a lot of stress on our environment, about a five out of ten.

We have had no problems with the code levels, or anything else. We get the occasional bugs as everybody does, but the code, overall, has been really good for us.

The stability has been really good. It has only been deployed for about three months, but they have had no issue so far.

It is pretty stable. We do not put too much stress on it (about 45 percent).

The stability is very good for us because it is required for our operations. We have had no problems with it.