What is your primary use case for NetApp Cloud Volumes ONTAP?

The solution helps to keep production data.

We use it mostly for distributed files. For example, one of our customers is in construction. So they have centralized NetApp storage and set up replication with the Cloud volume ONTAP. Several branch users access the Cloud instance. And whatever work that they do on the Civeo instant gets replicated to the client's data center on the on-premise NetApp storage. And they use GFC with Seavio for a seamless experience.

I work for the government, so all of our information is classified. We do a lot of on-prem with NetApp backup storage. I'm also interested in the recovery features. I'm going to take that back to the team and see what we can do with that. The upgrades, storage, and recovery features are some of the big aspects we discussed two weeks ago. We have an overflow in other locations that I can't talk about. We had a bunch of questions about what we would do in the event of a disaster to recover data that's been there for the past 15 to 20 years.

We use CVO for NFS data storage, NFS sharing, and SMP sharing.

The solution is used for NAS, which includes CIFs and NFS.

Companies that want to move to the cloud want to have a DR in the cloud. However, moving a file share is very tough and requires a lot of work from scratch. If you have NetApp Cloud Volumes ONTAP and if you have an on-premises storage scenario, it's very easy to replicate the workload from the cloud using the native application tool. You don't need to reengineer everything. It's very useful, and efficient. If you use deduplication and compression on-premises, you will be able to do the same on the cloud. NetApp Cloud Volumes ONTAP also helps save money in terms of file shares and storage. For example, if you have 50 TB of data, you will be able to compress it and pay for 25 TB of data. You have control over configuration and retention as well. You can keep data for longer because of the in-built backup feature.

The primary use case is for a transition off of our on-premises ONTAP and secondarily to add functionality as we migrate.

The solution is for file sharing and networks. If we have a cluster in a network, for example, two servers needed to use a common file, NetApp is a good tool. You can spin up a network from the other cluster, so if your application is a multi-node cluster and you need a common place to share the drag with, you can use NetApp for that.

We use it to monitor our on-prem and our SnapMirror between one and the other.

My employer is a partner here in Brazil. We have clients using many different versions of the solution. Some clients are using private clouds and hybrid clouds. Our clients use the solution as a Direct Access Recovery (DAR).

Our primary use case is for shared storage. We use the solution to support our ERP environment, where our teams want to share storage between different servers/apps. We're mostly using it for NAS.

Our organization utilizes a hybrid cloud in which Cloud Volumes ONTAP is a single node. We have multiple instances of Cloud Volumes on a single node in AWS, and we primarily use it to take snapshots for disaster recovery. We save many snapshots at that location so we can redirect users if something happens on our primary site. The other use case is backup. We enabled SnapLock, which acts as the WORM, making those snapshots immutable. In other words, they can't be deleted. Those are the two use cases. One is disaster recovery, and the other is to preserve a third copy of the snapshot. This is typically for Tier 1 applications. We have a third copy, and no one can delete the volume's snapshot. The end-users don't work with Cloud Volumes directly, but if our operational team needs to restore some files that aren't on-prem, they sometimes go to those instances in Cloud Volumes. That's only when they have to restore something beyond the date range of the on-prem snapshot.

We use it to store all kinds of data, both structured and unstructured.

We store our user documentation repository in NetApp. We are serving multiple divisions, and there are use cases grouped by divisions, by user access rights, et cetera. We also have specific requirements for the backups and restores.

We are using it for Virtual Desktop Infrastructure in AWS. I believe we're using the latest version.

It is managing services in our production environment that are in Azure. It provides file shares, both NFS and CIFS, that are used by other applications that are also in Azure. NetApp Cloud Volumes ONTAP is part of the production environment of our company so the entire company, over 5,000 employees globally, is touching it somehow. It's a part of an application that has data that resides on it and they may consume that application.

NetApp Cloud Volumes ONTAP is where we host our NAS storage on which we keep our files, et cetera. We have three clusters of CVO, each serving close to 300 terabytes of data. We have our SQL backup workloads and the application data residing in it. We are using the tiering policy, which pushes the inactive data down to cold storage to help save on costs. Cloud Volumes ONTAP is all cloud-based and we have our workloads on Azure.

We use Cloud Volumes ONTAP to back up ONTAP Select instances from our plants and distribution centers to Cloud Volumes ONTAP and Azure. We store a backup solution for all or most sites.

The primary use case is to use NetApp Cloud Volumes ONTAP for unstructured data storage, both for Windows and Linux-based machines. We use both from an NAS functionality perspective, along with SMB and NFS file shares/exports, for storing unstructured data.

We mostly use it for disaster recovery.

Our use case is to have multitenant deployment of shared storage, specifically network-attached storage (NAS). This file share is used by applications that are very heavy with a very high throughput. Also, an application needs to be able to sustain the read/write throughput and persistent volume. Cloud Volumes ONTAP helps us to get the required performance from our applications. We just got done with our PoC. We are now engaging with NetApp CVO to get this solution rolled out (deployment) and do hosting for our customers on top of that.

I work as a cloud architect in the multicloud team. We have customers that run NetApp services like CVS or CVO on Google or AWS or Microsoft Azure. We help them, support them, and we do migrations from their prime workflows to the cloud. The primary use case is the migration of workloads from on-prem to cloud. We use the SnapMirror functionality to move to GCP, for example. The second use case is that we also have some file services which we need on the cloud platforms. Our customers use file services like NFS and CIFS or SMB to address their requirements.

We are predominantly using it as a backup target for our products. We are also doing some CIFS shares to remote sites that don't have their own file server infrastructures.

We use NetApp for our on-premise file shares, and we use Cloud Volumes ONTAP as an offsite backup copy.

The main use case of ONTAP is for users to utilize SharePoint. From there, they need to access data where there are specific applications as well as an individual shared folder. It is being used for application purposes as well as for individual user purposes. We are using the latest version.

We use the solution on premises for files and in AWS for the target.

The primary use case is storage of medical records.

The primary use case for our customer is disaster recovery. They had an array that was reaching end-of-life, and they were trying to decide whether to go with a refreshed new array on-premises or go with CVO in a cloud. The chose the latter.

My primary use case of ONTAP is for all of my data.

Our primary use for this solution is disaster recovery. We protect our data by replicating using SnapMirror and storing it in a public cloud.

We use this solution to manage all of our NetApp storage. We have been having good luck with this solution's snapshot copies and thin clones, in terms of operational recovery. We are looking forward to encryption for the snapshots. Our version does not support inline encryption using SnapMirror, so we're not at that point yet. With respect to this solution's unified file and block storage access, we only use block-storage and it fits the needs of our customers. We serve internal customer bases, which feed the customers on the outside. For us, it is the right fit. We don't have anything in the Hyperscaler environment right now. Everything is internal to us.

We use this solution both on-premises and in the cloud. Our primary use case for our on-premises implementation is production data and DR. In our cloud implementation, we use this solution for DR. Moving to the cloud version was something that was different for us, but it was a fairly easy transition. Once we got comfortable with it, now it's second nature. There are many new features and I find that it is more valuable. In terms of operational recovery, the solution’s Snapshot copies and thin clones are easy to do. It greatly simplifies DR testing or application testing because we can very quickly clone a volume provided to the application team. They can use it, and if they want to keep it then we'll split it off and they have their own volume. Or, if they don't want to use it then we just throw it away. With respect to using inline encryption using SnapMirror, this is something that we are interested in but our version does not support it. Once we upgrade to a supporting version, we plan to deploy it. The solution's unified file and block storage access give us a standard common interface and a set of tools that we use regardless of whether we're dealing with the cloud or on-premises. The solution’s Snapshot copies and thin clones have greatly improved our application development speed. The DBAs can create clones on their own and do whatever they want with them. They can keep them, destroy them, split them, etc. It takes a load off of the storage administrators and puts it where it really should be. The consistency of storage management across clouds has made our storage operations a lot simpler. We didn't have to learn new interfaces and new command sets. Everything that we're used to using on-premises works for us in the cloud. With respect to our data footprint in the cloud, we are seeing all of the storage benefits being extended from what we have on-premises. We're just getting into the cloud now, and we're probably seeing between a thirty and fifty percent reduction in our data footprint using compression, compaction, and deduplication.

Our primary use case is data replication to the cloud.

Our primary use case for ONTAP is for DR.

We use this primarily to consolidate our services and block services.

The primary use case is for files, VMware storage, and the DR volume on the cloud. They also use this solution to move data between on-premises and the cloud volume ONTAP.

Desktop-as-a-service is a PoC that I'm doing for our customers to allow them to use NetApp for their personal, departmental, and profile shares. This connects their desktop-as-a-service that we're building for them. This is for training. The customer has classrooms that they have set up. They have about 150,000 users coming through. They want to have a way to do a secure, efficient solution that can be repeated after they finish this class, before the next class comes in, and use a NetApp CVO as well as some desktop services off of the AWS. It is hosted by AWS. Then, it hosted by CVO who sets out some filers, as well Cloud Volumes Manager as well. We were looking at it with Azure as well, because it doesn't matter. We want to do a multicloud with it.

The primary use is virtualization as well as filer storage, pretty much all the features of the ONTAP suite. We don't have any cloud footprint for contractual obligations. So, it's all pretty much on-prem, but it's in a co-location.

Our primary use case is for multiprotocol access.

We're trying to see whether it's a good fit to move our secondary storage to the cloud, which would then be in competition with ONTAP Cloud Volumes. However, ONTAP gives us a bit more flexibility. If it's cost-effective, good enough performance, and has all the tools we need, we will continue with it. So far it looks great.

The primary use case is to move age old data to the cloud. It is deployed on the cloud.

For the most part, we're using it to move data off-prem. We have the ability to do mirrors from on-prem to Cloud Volumes ONTAP and we also have both single-node instances and HA instances. We are running it in both AWS and Azure. We're using all of the management tools that go along with it. We're using both OnCommand Cloud Manager and OnCommand Unified Manager, which means we can launch System Manager as well. Unified Manager is what monitors the environment. OnCommand Cloud Manager allows you to deploy and it does have some monitoring capabilities, but it's not like Unified Manager. And from OnCommand Cloud Manager you can launch System Manager, which gives you the lower-level details of the environment. Cloud Manager will allow you to create volumes, do CIFS shares, NFS mounts, and create aggregates. But the rest of the networking components and other work for the SVMs and doing other configurations are normally done at that lower level. System Manager is where you would do that, whereas Unified Manager allows you to monitor the entire environment. Say I have 30 instances running out there. Unified Manager allows me to monitor all 30 instances for things like volume-full alerts, near volume-full alerts, I-nodes, full network components being offline, paths, back-end storage paths, aggregate fulls. All those items that you would want to monitor for a healthy environment are handled through Unified Manager.

The primary use case is for SAP production environments. We are running the shared file systems for our SAP systems on it.

We are using it for storing files, to get high-performance access to files. We are also using NetApp for DR. We copy the information to the same system in other regions.

Our primary usage is as a repository for the application servers. It's mostly for NFS, with very good replication options and backup features. There are also tools that we need to put there and replicate between our on-prem and AWS locations.

The tool integrates very well the contents that are deployed there. Each aspect is well structured and responsibly what allows it to advance and achieve success.

Lo usamos para la seguridad en la navegación y la administración de fuentes de datos alternativas con el fin de mantener activos todos los procesos.

The primary use case for ONTAP is both on-premise and in the cloud. For on-premise, we utilize it for hosting our virtual infrastructure environment through VMware, as well as hosting personal and shared drives. Then, in the cloud, we also host personal and shared drives within AWS and Azure.

We use it for the data that we are using, etc. We have a dedicated team of 10 people who manage the storage.

We use it for file storage. It is mainly being used with our Windows environment.

The primary use case of NetApp in our company is providing NAS services. This includes both CIFS and NFS. I have been working with ONTAP for five years. So, I started with NetApp ONTAP 7-Mode, and now, I'm working on NetApp ONTAP C-mode. My familiarity and skill with this product is quite good. Autodesk has been using this product for more than five years.

It provides flexibility for our VM environments. We use it to transport data between on-premise systems and the cloud. AWS is the biggest and most common use case for integration with ONTAP.

We use it for file services, both CIFS and NFS.