There is a team of four people who are in the role of managing and administrating the devices. There are thousands of people who access it.

There is room for growth. We are just in the process of migrating an on-premise system. That will probably service 10,000 users. We started out using it mainly for unstructured data which would be less frequently used or Azure-native. Now, we are at the process of expansion. After using the product for a year and a half, we are comfortable migrating on-premises into our system.

I rate NetApp CVO 10 out of 10 for scalability. We can get more capacity on demand.

NetApp has to make improvements on the scalability. It is not really scalable for a bigger scope because of many reasons. NetApp is limited to using six disks and the biggest disk size that they can use is just 16 terabytes. Six disks with 16 terabytes is not enough for a big environment. Right now, NetApp CVO can accept 350 terabytes, but it is 350 terabytes including tiering. In many cases, this is not enough for big data.

In an HA environment, it will scale up to 358 terabytes. That's not bad per-system. We've had no difficulties.

We will be moving more stuff off-prem into the cloud. Right now it's at about 15 percent of our entire environment, and we plan on at least 10 percent, or more, per quarter, over the next few years.

We'll be doing the tiering and using the Cloud Sync as well. We're a financial and insurance company, so some things have to remain on-prem, and some things, from a PCI perspective, have a lot of different requirements around them. And because we're across multiple countries worldwide, there are all sorts of HIPAA and other types of legal and financial ramifications from a security perspective. In the UK and in Europe there are the privacy components. There are different things in Hong Kong and Singapore, in Spain, etc. Each country unit requires different types of policies to be adhered to. Everything we have is encrypted at rest, as well as encrypted in-flight.

Cloud Volumes ONTAP will also support doing data encryption at a volume level, a software encryption. But from a PCI perspective, we use the NSE drives, which give us hardware encryption. So they're double encrypted. They are hardware encrypted. We're having to use a management appliance to keep and maintain the encryption keys, and we do quarterly encryption-key replacement. But there are also the volumes that are encrypted as well. We also use TLS for transporting the data, doing encryption in-flight. There are all sorts of things that it supports which allow you to be compliant.

Another feature it has is disk sanitize, a destruction component which allows you to do a DoD wipe of the data. Once you've decommissioned an environment, it is completely wiped so nobody can get access to the data that was there previously. That's all built into Data ONTAP, including Cloud Volumes.

NSE drives are a little different because you are not getting physical drives in the cloud environment, so you couldn't do that. But you can do the volume encryption, from Cloud Volumes. In terms of a DoD wipe, you wouldn't be doing that on Azure's or AWS's environments because it's a virtual disk.

Scaling CVO is straightforward. It's super easy to grow the cloud environment compared to the on-prem solution. It's easier to scale.

You can scale vertically and horizontally, and I'd give scalability a rating of ten out of ten. The clients who use NetApp Cloud Volumes ONTAP are enterprise companies.

We only have a few systems in it. We have two on-prem clusters, one CVO instance, and an S3 instance, which I don't have a connection to yet. There's something wrong with the configuration or firewall risk or going into S3. Then, we'll have our FSX one built into it when we get to that point.

Scalability has been a trouble-free experience. When we decided to increase our storage capacity by incorporating an additional drive shelf, the engineer collaborated with us, and the expansion process was executed smoothly, ensuring there was no downtime or interference with our production operations.

Regarding scalability, it performs admirably. I haven't encountered any issues with its ability to scale. However, it's worth noting that NetApp faces stiff competition in the realm of private channel solutions.

Cloud Volumes added an option to stack licenses to increase capacity. Before, you were only allowed one license per instance, which gave you 360 terabytes. Now, you can stack the licenses to add a second license of the same instance to get another 360 terabytes, totaling 720. 

That's vertical scalability, but we haven't scaled horizontally. We just use it for a single node per instance. We started with one instance, and now we are on the seventh. As we add new on-prem projects, they always require a copy of their data somewhere. That's when we deploy additional instances.

It is definitely scalable. You can add more disk to grow your capacity and you have the ability to add more nodes. There's a limit to how many nodes you can add, but you can definitely scale up.

NetApp is scalable. When we initially started with Cloud Volumes ONTAP, it had a hard limit of 378 terabytes as its maximum capacity per cluster. Beyond that you couldn't expand. So we had to spin up another cluster. When that was almost full we had to get a third cluster. But I believe that in the recent build of CVO they have introduced the ability to stack one license on top of another cluster, so you can have infinite data per cluster. So there were challenges, particularly with vertical scalability before, but that has now been fixed in the recent release.

In terms of increasing our usage in the future, we definitely will if required. It gives us the flexibility to perform automations and it has its own encryption tools. Right now, we are using it for one particular region in Europe, but we do have plans to get it out to other regions as well, but that's not going to happen immediately.

60 percent of our tape data is sitting in the cloud now.

There's a limitation to scalability. Right now, when you want to expand the initial architecture, we have to add additional loads just so it can handle the data without hurting the performance. Then, we have to go back and request for more licensing. It adds to our licensing, thus adding to the cost. In regards to scalability, unless you have a five to six year plan ahead, we can't say, "Great, we have run out of space. Okay, let's try to increase space." It's not like increasing volume.

NetApp is scalable. 

It's very scalable.

We focus on apps or IT services that are using it and currently the total is in the neighborhood of about five.

It is very easy to scale. It takes next to no time to be able to do that. It is very simple and easy to do that part. You just need to get a license and add the storage.

It is a very scalable solution. We are looking at how we can grow in the cloud and it can definitely scale in the cloud.

It is easy to scale. It is inherent to the actual product. It will move to another cloud solution or it can be managed from another cloud solution. So, it's taken down barriers which are sometimes put out by vendors in different ways.

We can expand on it as needed. In particular, it's easy to add storage, and storage expansion is probably the feature we utilize the most. We don't mess with any other features, like within the protocols or anything like that. Those are fine, but storage scalability is pretty good.

Our clients' storage needs vary. Typically, it's somewhere in the range of 20 to 30 terabytes, but at least 15 to 30 terabytes. Each client is a little different, but the one that uses the most storage has a capacity of about 30 terabytes.

Scalability comes down to what service or what NetApp Cloud solution you're using. There are different solutions for what you're trying to achieve. Based on your requirements, you just need to pick the right solution that works for you.

Scalability is there. You have to buy ahead shelves and everything else to keep it growing. It is fairly simple.

We are not using it at that big of a scale, so right now we do not have any concerns. It's limited to 360 terabytes. In the past, before we sold 80 percent of our company to that large company, we used to have more than 360 terabytes of data. If we still had all that data we would have to build another instance of Cloud Volumes ONTAP. Or, post-sale, if we were to cross that limit we could have to build another instance of Cloud Volumes ONTAP, but we're not there yet. We are using about 25 percent of that limit right now.

We still have CVO running on a single VM instance. As an improvement area, if CVO can come up with a scale out that will help so we will not be limited by the number of VMs in GCP. Behind one instance, we are adding a number of GCP disks. In some cases, we would like to have the option to scale out by adding more nodes in a cluster environment, like Dell EMC Isilon.

Scalability remains to be seen. At this time the NetApp limits on the levels of premium, standard, and the basic one are unreasonably incorrect.

It is hard to go from ten terabytes to three hundred and sixty-eight terabytes and leave everyone in between there hanging. Nobody is interested in going with the limit of ten terabytes to test this solution.

I am talking specifically about Azure, Cloud Volume ONTAP and the differentiator between three levels of provisioning storage.

The scalability is good to a point, but there is a hard limit on the capacity. We could, obviously, create another associated instance of it, but it wouldn't be a single name space, and we couldn't do some of the things you can do if you have a lot of multiple, real NetApps. So there are some hard limits to how big a solution you can create.

Day-to-day, it's probably only being used by about a dozen people in our organization, because it is mainly a backup target. There is a small collection of people whose shares live on it, but the majority of the business' files are on the real NetApps on their sites.

It's probably at a size where we're not likely to implement any more. You never know. It's very hard to tell what will go on with our company. But at the moment, it's probably not going to get any larger. We may actually shrink the capacity because we are temporarily storing some stuff for a part of the business that should only be on there for a few months at most, with this COVID.

As an organization, we went ahead wholehearted that anything and everything should be in the cloud — cloud first — and that got tempered a little bit because they started to see the costs. We also hit limitations with some of the software vendors because they're quite small companies and very niche. They don't want to support anything that's in the cloud, so there are limits to what you can put in the cloud.

Everything is fine with the scalability.

We have more than 10,000 people using the solution on the cloud. 

The company has more than seven filers and controllers each. 

There are four people managing Baxter International's storage in India and the UK. Two people manage this device, a senior technical associate and myself.

This product is very easy to scale.

Scalability is not an issue because it is really expandable. If you don't know the structure of the business you can scale up, scale down, and do everything graphically.

Right now, the scalability is sufficient in what it provides for us, but we can see that our customer environments are growing. We can see that it will reach its performance end in around a year or so. They will have to evolve or create some performance improvements or build some scale-up/scale-out capabilities into it.

In terms of increasing our usage, the tiering will be definitely used in production as soon as its GA for Azur. They're already playing with the Ultra SSDs, for performance improvements on the storage system itself. As soon as they become generally available by Microsoft, that will probably a feature we'll go to.

As for end-users, for us they are our customers. But the customers have several hundred or 1,000 users on the system. I don't really know how many end-users are ultimately using it, but we have about ten customers.

It's limited. We're trying to figure out better methods as we need to scale out more.

I rate the scalability a five out of ten. And in terms of storage, we have different types of storage like SSD, standard, SSD, premium, and SSD, which can expand the pool or aggregate. Also, the availability part and any payload are seamless. Plus, I have the same technology on-premises, so there is replication and SnapMirror. 

In our company, around 3000-4000 users are using the solution at present.

We have been pretty impressed with the scalability because when we started, we had to immediately onboard two more divisions and it was pretty straightforward, once we had the base setup going. We were able to scale it up pretty quickly and we were able to do it on our own.

We are using Cloud Volumes ONTAP daily. Our departments are copying the files on it and sharing them. It's a part of their daily work.

At the project level, we are not looking to expand our usage of NetApp, but at the organizational level, there are plans. They are looking at additional use cases that can be  onboarded to NetApp.

We have not had a scalability issue, so it scales easily. We are using about 20 terabytes. We have about 200 people who are using it on a day-to-day basis. They are mostly from the finance team.

We have plans to increase its usage. We are investigating it. It is all based on the business.

The scalability is great. You don't have to add controllers to add storage space and you can scale out if you need to add more horsepower to your cluster.

Our global footprint is, with reduction, about 300 terabytes. 

I haven't attempted any scaling yet.

Scalability is good.

Since it has seamless integration with AWS, scalability is not an issue.

It's completely scalable, as long as you're willing to buy the hardware. That's why we're looking at cloud for the future, so we can stop buying hardware and maybe use the cloud instead.

Its scalability is very good.

The solution is extremely scalable. For example, if you initially subscribe to one terabyte, and then all of a sudden, you need two terabytes, you can dynamically expand it. You can add a feature within NetApp, and it will automatically increase it for you. You never have to worry about the space getting out of control.

It scales well. We can add to the license. We have a 100 terabyte license right now, but we can add to it very quickly.

There is very low maintenance because once you deploy it, you run your scripts and you can see what failed and not many things fail. So, it's pretty quick.

The solution is definitely scalable on the cloud. On the cloud, you can scale almost infinitely. You don't have to worry about reaching any limits, so that's definitely very good. Also in performance levels, you can have underlying storage in the cloud allowing you to change the IOPS, or performance at latency on the fly. That is something you cannot do very easily on-premises.

Scalability is easy.

Both performance and scalability are really good. We started with a small system but have grown really fast. We needed to change the type of system and the license. We were able to do that online with no issues. Doing so, and going with the bigger type of system, also gives us better performance. 

So if you need more performance, you can always change the type of system. Working with NetApp, they provide us with a consultant, if needed, to determine what the best type of system is for our use case, based on the performance that we need. They're flexible.

We're growing all the time. We have several sites already and we're adding more sites when needed. We are keeping the on-prem as well because it doesn't always make sense to move to the cloud. It depends on budget, the CapEx and OpEx. But we are growing.

There are capacity limits. It has a maximum of 368 terabytes.

We're not that big, storage footprint-wise. However, it's simple. You just add nodes. So, it works.

Scalability is a very good feature. If our data reaches 90 percent (or some threshold level), it automatically increases the storage within ONTAP without our intervention.

The solution helps us control storage costs. It is scalable. If we need more storage, then we can opt for a monthly or yearly option.

This is another issue that we like from ONTAP. There are products for different scales. It is very easy to use.

It's very scalable. I even insisted when we ordered the latest ones that we get the interconnect switches. So, if we want to expand, we already have those in place.

The scalability is very good. Our environment is about 20TB.

We still haven't needed to scale up, but I think the scalability is good.

We are using it for a system which stores files and parts of databases, but the system is used by hundreds of customers. NetApp is not used directly by them, rather through the system. We may plan to increase NetApp according to the usage of the system but we still have no specific plans.

Lo usamos en toda la empresa.

The scalability of NetApp is good. In NetApp, we have close to three petabytes of data.

We cannot compare the scalability of the on-premise solution with the cloud solution because cloud works in a different way from the on-premise version. 

When it comes to the logical partitions, the scalability is fine. Though, after a set time limit, you need to procure physical boxes to increase your storage capacity.

We haven't hit the upper boundaries of the solution, so I don't think that scalability is going to be a problem for us in the near future.

Scalability is very good. If they need to expand then that is one of the features of this solution, easy expansion. We haven't seen any issues there. They haven't expanded it yet, but certainly, the functionality exists.

The scalability is very good. Our environment is 25TBs.

ONTAP makes it easy to scale our infrastructure. It is important for us because our business has increased rapidly.