The solution enabled us to deliver on our cloud-first strategy. It also provided us some savings and consolidation capabilities from a volume perspective where we can run with less management. We can run higher volumes of unstructured data and store higher volumes of unstructured data as compared to other solutions.

CVO gives us the ability to access data as quickly as possible, which is critical because of the mission set we handle. Some things cannot wait. For example, we tried having the data in the cloud itself, but it took too long for us to retrieve it from cold or deep storage. If we have it ONTAP or on-prem, it's so much easier to pull it within minutes. 

CVO has reduced the amount of storage significantly. The solution has saved costs. We've done a cost analysis of on-prem and then the cloud. On-prem is where it's at for our mission. Some organizations can store their data in the cloud and not access it for years. We need data constantly and require the ability to dig into data from five to 10 years ago. 

It is much easier to control data since we can run queries across all our platforms with just one solution. Not only that, we can also monitor all the platforms with Active IQ, where we can see all the alerts, messages, and space consumption through a single application. This is regardless if the data is on-prem or AWS. It is much more efficient. 

We're sitting at multiple petabytes of storage on our NetApp infrastructure. We're talking hundreds of thousands of shares across thousands of volumes. Even with that size of infrastructure, it's being supported by three people. And it's not like we're working 24/7. It gives us the ability to do a lot, to do more with less. Those three people manage our entire NAS environment. I've got two intermediate and one senior storage engineer in our environment who handle things. They're handling those multiple petabytes of on-prem and I'm just starting to get them involved in the cloud version, Cloud Volumes ONTAP. So, for the most part, it's just me on the Cloud Volume side.

In terms of the storage efficiency reducing our storage footprint, the answer I'd like to say is "yes." The problem I have is that nobody ever wants to delete anything. We have terabytes of data on-prem in multiple locations, in both primary and DR backed-up. And now, we're migrating it to the cloud. But eventually, the answer will be yes.

CVO helped us migrate to the cloud. We were already using the same software on-prem. We just migrated it to the cloud, so it helped us with that. 

The workload migration was outstanding. It was seamless. We have on-premise CVO within BlueXP. We just drag and drop the on-premise workload to the cloud workload. It just migrated and cut over. That was it. The time required depends on the volume size. Our largest volume took us three-and-a-half weeks. It takes some time to migrate the data from on-prem to the cloud. 

We have on-prem NetApp AFF, and we're looking into using NetApp Data Sense or Blue XP Data Sense for the backup servers as well. Everything integrates perfectly. We have some on-prem workloads that run on NetApp, and CVO on a cloud. We can migrate between the two if needed.

It's a single pane of glass where we can see our applications running. 

The transition to the AFF storage solution significantly improved our organization by reducing our physical footprint. We went from a FAS system with two controllers and twenty drive shelves to just four controllers and two drive shelves with the AFF. This led to substantial reductions in power consumption and space requirements in our data center.

The main benefit we get from this product is the ability to deploy it anywhere we want, whether that's on-prem, a remote physical location, or in the cloud. It doesn't matter from an operational perspective where it is. The command line and operating system are the same. 

If I give it to someone to manage, they don't know if the product is running in the cloud or on the physical location. That's great because you don't have to worry about knowledge transfer. The product runs the same regardless of how it's deployed. Cloud Volumes has also significantly improved performance and storage efficiency because it has capacity tiering, which is helpful if you're cost-conscious. 

It provides unified storage, so you can use it for NAS or block. However, we segregate a separate cluster for files and another for block storage. Fortunately, it's the same ONTAP operating system, so a user doesn't need to understand a different set of command lines or another method if dealing with block storage or files. It's all the same for them.

It helps us manage our native cloud storage. Cloud Volumes allows us to choose which storage types are applicable for us. In our case, it lets us choose a cheaper EBS storage, and then we can perform capacity tiering in S3. It gives us the flexibility to determine which type of native AWS storage to use, which is cool.

Cloud Volumes ONTAP is great because of the storage efficiencies that it provides. When you look at the cost of running Azure native storage versus the cost of Cloud Volumes ONTAP, you end up saving money with Cloud Volumes ONTAP. That's a big win because cost is a huge factor when putting workloads in the cloud. We had a cost estimate survey done, a comparison between the two, and I believe that Cloud Volumes ONTAP saves us close to 30 percent compared to the Azure native costs.

Azure pricing is done in a type of a tier. Once you exceed a certain amount of storage, your cost goes down. So the more data you store, the more you're going to end up saving.

The storage efficiencies from the NetApp platform allow you to do inline deduplication and compaction of data. All of this adds up to using less of the disk in Azure, which adds up to savings.

We have two nodes of the NetApp in Azure, which means we have some fault tolerance. That is helpful because Azure just updates stuff when they want to and you're not always able to stop them or schedule it at a later time. Having two CVO nodes is helpful to keep the business up when Azure is doing their maintenance.

The solution provides unified storage no matter what kind of data you have. We were already using the NetApp platform on our on-premise environments, so it's something we're already familiar with in terms of how to manage permissions on different types of volumes, whether it's an NFS export or a CIFS share. We're able to utilize iSCSI data stores if we need to attach a volume directly to a VM. It allows us to continue to do what we're already familiar with in the NetApp environment. Now we can do them in Azure as well.

It enables us to manage our native cloud storage better than if we used the management options provided by the native cloud service. With CVO, all of your data shares and volumes are on the one NetApp platform. Whether you are adjusting share permissions on an NFS export or a CIFS share, you can do it all from within the NetApp management interface. That's much easier than the Azure native, where you may have to go to two or three different screens to do the same stuff.

At one point we were paying close to $80,000 a month for cloud resources, and now it's down to $25,000 to $30,000 after using the tiering.

Also, using Unified Manager we are able to resolve issues before they have an impact. For example, there were conditions where bulk operations were happening against a particular volume, and our business was also writing the data. We caught it using Unified Manager. The IOPS were low and there was a high latency, close to 1,500 milliseconds. We had a look at exactly what operations were happening and, before the user even reported it, we reached out to the team that was doing the bulk operations to stop whatever process they were running. That's just one example. We have had a lot of occasions where the tool has been really handy when it comes to proactive monitoring. 

And it's not only for proactive monitoring. The same tool is also used for a lot of root cause analysis.

The tool saves us time and money. Now, it's easy to retrieve data back, where you can go back and look at the statistics to study them. Because my company is focused on healthcare, there's no time limit on the retention of information. It's infinite. So, instead of having all our data on tapes and things, which takes many hours to try to retrieve information back. This is a good solution.

By implementing this solution, we wanted to achieve simplicity. We were trying to get away from reconfiguring everything all the time to work so that we could just get down and implement things within a very small window of time. They would not require a lot of reconfiguring each time.

The main benefit is accessibility. We are able to access it from anywhere. We are able to move things to what we need or are able to pull back the data when it is needed very quickly. We can restore the databases when I need to.

We have a single pane of glass. It helps a lot because time is always the essence. The simplicity comes in handy. It saves quite a bit of time. I do not have to sit down and do all the things. I am able to go in and hit a couple of things. I can deploy, modify, or do whatever needs to be done. It takes seconds versus hours. Once you learn the tool, it is very simple to work from the same point. When it first came out, it was very clunky. It took some time. It took some learning, whereas now, you can catch up pretty quickly. After you start to fine-tune it a little bit, you are able to work with it. Earlier, it was a pain.

I can see how much storage I have left and what I am working with. I can see the alerts. It gives me time to start working on what I need to procure at that point.

It has helped to right-size our workloads. It has been great. It has significantly dropped our downtime for volumes and improved the access for clients. It has helped out a lot in those aspects, so I can stay ahead of the game instead of behind the game. That is where that tool comes in handy. 

It is great when it comes down to pinpointing problem areas. It catches things before they become a problem, so I can keep my clients up and going and functioning. It has been great in that aspect.

I am a big fan of analytics because they give me the chance to be able to keep the clients up and going. That is my biggest thing because when they are down, we lose a lot of money, and we lose a lot of clients, so the ability to make sure that I am up almost 100% percent and being able to stay ahead of the game is a huge win for us.

The way that it has helped our organization is that it requires less time to manage. It's almost like a set-it-and-forget-it type of solution. We don't have to do too much maintenance. Compared to other products, it doesn't need so much babysitting. It's easy to set up and it works. It does the things it is expected to do.

In addition, it provides unified storage no matter what kind of data you have. It has multi-protocol support. It does shares and it does block, so it's a one-stop solution that can fit all of your needs. You don't need multiple solutions for your different types of data.

We haven't put it into production yet. However, in the proof of concept, we show the use of it and the how you can take it in Snapshot daily coverage, because we're doing it for a training area. This allows them to return back to where they were. The bigger thing is if they need to reset up for a class, then we can have a goal copied or flip back where they need to be.

It gives a solution for storage one place to go across everything. So, the customer is very familiar with NetApp on-prem. It allows them to gain access to the file piece. It helps them with the training aspect of it, so they don't have to relearn something new. They already know this product. They just have to learn some widgets or what it's like in the cloud to operate and deploy it in different ways.

The customer knows the product. They don't have to train their administrators on how to do things. They are very familiar with that piece of it. Then, the deduplication, compression, and compaction are all things that you would get from moving to a CVO and the cloud itself. That is something that they really enjoy because now they're getting a lot of cost savings off of it. We anticipate cloud cost savings, but it is not in production yet. It should be about a 30 percent savings. If it is a 30 percent or better savings, then it is a big win for the customer and for us.

Our clients see most of the benefits. Cloud Volumes ONTAP provides offsite backups. We used to host our backups on physical infrastructure in a data center or on remote sites. There were a lot of storage costs for replication. By implementing Cloud Volumes ONTAP in the Azure portal, we eliminated the cost of additional hardware and everything you have to maintain on-prem in a physical environment and put it up to the cloud. That was a considerable cost savings for the customer.

Cloud Volumes ONTAP is a massive improvement in terms of manageability. It's easier for customers to perform certain functions from that interface, knowing it sits on a high availability platform. We don't worry about paying all these separate vendors for replication solutions. Other costs are associated with maintaining physical infrastructure in a data center, like electricity or storage space, RAM, and other hardware. It has improved our clients' bottom line because they spend less on disaster recovery.

ONTAP has improved my organization because we no longer need to purchase all that hardware and have that all come up as a big expense. It worked out better for our budgeting purposes.

We use it to move data between hyperscales on our on-premises environment. We're able to do that with SnapMirror and it's pretty simple to set up and move data around. 

In some places, it helps to reduce the amount of our storage, but a lot of our data is very active and in very small files, so the system does not have enough time to keep track of all that. In one instance, we had a job, and we dumped roughly 25 terabytes in a day into the system, so for it to understand and try to reduce it and compress it, it sometimes does not have time because it is just so busy.

It has saved us on costs. I am not on the manager's side, but I have seen that the cost is better. I do not have the exact numbers, but it is probably two or three dollars per terabyte or something in that realm. Some of our competitors cannot beat that, so that does help.

Being able to deploy in AWS is a big advantage for us. The company I work for was recently spun off as a smaller company. We sold most of our company to a large company and all of our assets went to that company. Then we started building our first data center and we did not have a second data center for our outside copy. This was a great solution in these circumstances.

In general, NetApp provides unified storage, but we mostly use it only for NAS. It gives us great control over our data. We can define which region or zone we put our data in, in AWS. That way, we can strategically place our offsite copies. Instead of putting everything in one place, we now have more freedom to put data wherever we want.

We are also saving at least $100,000 a year on storage costs.

Using this solution, the more data that we store, the more money we can save.

It's meant to do the same thing in the public cloud that we were doing in our private cloud. In the private cloud we can control the infrastructure, whereas in the public cloud we don't have as much control. This gives us a way to optimize resource usage in the public cloud, without overpaying or wasting resources.

It also provides unified storage no matter what data you have. It makes sure we have control of the data and that we know what it's being used for. The main thing for us is that we need to know what applications are consuming it and responsible for it. The solution helps us do that.

In addition, it helps us because we know what it's used for, who owns something, and who's accountable for those storage costs. Ultimately, it helps us reduce our storage needs and that's where we get our savings.

Compared to native cloud storage, NetApp Cloud Volumes ONTAP allows us to better manage shared storage.

It's difficult to say if it has helped to reduce the company's data in the cloud right now without running it for a while. It's the same for the cloud costs.

We are going through testing right now, and can't tell if it will affect their operations until we validate it.

It gives us flexibility. In a disaster situation, or even in an office relocation, there can be a gap. NetApp CVO allows us to continue to provide service customers with access to their data, even if a physical site is going to be down for a long period of time. It's only really viable if you know a site is going to be down for a long period of time. We've had office relocations and there have been gaps between when the old office closed and the new office opened, during that period of moving stuff over and setting things up. There were a couple of weeks where we were serving the data out of the cloud, rather than out of the physical site. NetApp CVO may have improved our uptime by 1 or 2 percent, because we don't have that much downtime to start with.

It has all the advantages of the real NetApp product. You can provide storage in most of the formats you'd want. 

It helps us to keep control of storage costs because it's an OpEx-based model rather than a CapEx-based model. It depends on how you license it. You can have it up and down, almost on an hourly basis. Obviously, we don't do that, we've got it up long-term. But it does have that flexibility to bring up an instance of a client filer for just a short period of time.

It has saved us from having to buy and host another filer somewhere. That would be the only option to achieve the same goal. If we were to buy another filer to provision the capacity we've got in the cloud, the CapEx would probably be at least $200,000, whereas the running costs are not that much. It depends on how you deal with AWS, but we don't pay that kind of money. It probably saves us 75 percent of the cost of buying a filer for real.

We are using Cloud Volumes only for our NAS storage, not FAS, which includes Windows, Linux, Solaris, and VMware.

We are remotely able to manage data.

We have performance monitoring, but there is not much load. Sometimes, we use it to trace performance when there are performance-related issues. We will then log a case based on what needs to be checked, like a network issue.

We are definitely in the process of reducing our footprint on our secondary data center and all those snapshots technically reduce tape backup. That's from the protection perspective, but as far as files, it's much easier to use and manage and it's faster, too.

The solution has definitely helped reduce our organization's data footprint in the cloud. The data-tiering helps a lot. I would say improving data tiering to S3 reduces our footprint by about 90-95%, which is huge. That is instead of just sitting on EBS, which is expensive storage.

Using Snapshot copies and thin clones for operational recovery is convenient. This technology makes things very easy.

The unified file and block-storage access across clouds and on-premises infrastructure have made things easier for us. It means that we do not face significant roadblocks.

It's helped us to dive into the cloud very fast. We didn't have to change any automations which we already had. We didn't have to change any processes we already had. We were able to adopt it very fast. It was a huge benefit for us to use the same concepts in the cloud as we do on-premise. We're running our environment very efficiently, and it was very helpful that our staff, our operators, didn't have to learn new systems. They have the same processes, all the same knowledge they had before. It was very easy and fast.

We did a comparison, of course, and it was cheaper to have Cloud Volumes ONTAP running with the deduplication and compression, compared to storing everything, for example, on HA disks and have a server running all the time as well. And that was not even for the biggest environment.

The data tiering saves us money because it offloads all the code data to the Blob Storage. However, we use the HA version and data tiering just came to HA with version 9.6 and we are not on 9.6 in our production environment. It's still on RC, the pre-release, and not on GA release. In our testing we have seen that it saves a lot of money, but our production systems are not there yet.

It just gives us the capability to get cloud resources.

The primary use case for ONTAP Cloud is getting data into the cloud.

We are using the product for our future planning in the following:

• Disaster recovery in the cloud
• Backup in the cloud
• Development in the cloud.

The solution works the same on the cloud as on on-premises, so we sometimes access the on-premises features even though we use the cloud version. There is hardly any difference. However, the performance depends on the disc type used and the network.

The main use case for us in going with Cloud Volumes ONTAP was to ensure the IOPS or performance. There are other solutions available that are probably more cost-effective than NetApp, but given the criticality of our application, the performance expectations, and the availability, those were the factors that helped us to zero in on the NetApp solution.

We were able to move our VDI environment into AWS. It has been a big performance boost. It has helped our customers all around the globe access virtual desktop.

Upgrades are much easier in terms of upgrading ONTAP. It is so much easier with CVO.

It provides unified storage and gives us better access to our data. We're able to manage it. I don't really see that any different than the on-prem solution, but it does give us the ability to manage access and permissions.

CVO enables us to manage our native cloud storage better than if we used management options provided by AWS. That's because we're more familiar with ONTAP. So, it is not like we had to change how we manage storage. That was the big thing, and it has an easier user interface. Managing AWS storage is also pretty easy, but to me, the easiest thing was the fact that we're familiar with ONTAP.

This solution has made everything easier to do. The most basic operations are very simple and we've been using NetApp tools, plus some of our in-house tools, to automate a lot of the processes. It saves us a lot of time and effort.

It helps us with our snapshots with our backups. We do a lot of SnapVault backups to our secondary data center and that is very efficient for us. It reduced our recovery time.

ONTAP has reduced our company's footprint on the cloud and has reduced our cloud costs.

We have a number of systems that we run on-premise and have not been moved to AWS for various reasons. ONTAP allows us to manage our portfolio across two domains. 

The university didn't have a centralized file service before we moved to NetApp. Now, departments can share information across 24,000 students, across 10,000 faculty and staff. They can share data without doing it through email, which was the old way.

It has definitely helped reduce the overall costs of storage. We actually started out with the IBM M-Series seven years back. We switched to NetApp. The same hardware from NetApp is a better price than it was through IBM, and the support is better. So it has reduced our expenses through that path. And since it's so easily supported, we don't need a lot of people to support it, so our support costs are lower.

We've had a lot of centralization going on. We have 13 schools, each of which had its own IT department. All those IT departments are now out of business because their work has been centralized into our department. Part of that was due to the economy changing and the school changing its business models, but that put our NetApp storage heavily into use. So it's hard to distinguish cause and effect.

I can't specify the amount of space saved, but the deduplication and compression in ONTAP are very effective. We're probably getting 35 - 40 percent savings because of dedupe and compression. And because every volume we put out is a quoted Qtree on a volume, we don't have wasted whitespace. I'm billing for 800 terabytes every single month, that's running on one petabyte of rotating disk. So, it's very good at saving me space. I'm running with about 20 percent available disk, above and beyond what I'm billing. So it's pretty good at that.

We're charging four cents per gigabyte per month and, unfortunately, I'm making money at that rate. We're not allowed to make a profit. I've been looking at reducing what we're charging our customers because it is so cost-effective.

At the time we implemented it, there wasn't any other solution. We needed a cluster, and we needed a common place where both nodes can share a file. There was not a good solution at that time besides NetApp. Now, there is. There's EFS. EFS is for Linux only. NetApp works for Windows. However, now, AWS is competing with NetApp with FSx. However, NetApp also has a feature for FSx.

In terms of how this solution has improved my organization, we use a third-party backup solution, like Spectrum Protect from IBM to backup finances. That's not the best way to do it. Our choice was to move from that technology straight to using the same technology for backup, which is essentially NetApp. Cloud Volumes ONTAP is NetApp. It's the same technology which is where the efficiency really is. It's much more efficient than using a third-party solution.

It provides unified storage no matter what kind of data we have. Right now, it's just backing up Volumes but NetApp is a unified solution. In our case, it's really for file storage, NFS or CIFS.

Cloud Volumes ONTAP allows us to keep more backup. We can keep more backup because of the cost of storage in Azure versus what we have in our data center. This is also completely off-site from our data centers. We have two data centers close to each other, but this actually keeps us as an offsite copy too because it's far enough away. It does keep control of our storage costs from a previous backup technology because it's kept in Azure and it's cloud-based storage. It's not our on-premise storage, it's kind of a hybrid cloud solution.

We're saving around 20% on storage. 

ONTAP made us less reliant on in-house hardware. It has already changed the way we're looking at our investments, purchasing plans, and budgeting for the next three to five years. We are shifting more into the cloud OpEx rather than keeping our expenses on the hardware side. That is already a good outlook.

We're just using AWS for now, but the consistency of storage management between our own program and the cloud seems to be great.

The solution has definitely helped reduce our company's data footprint in the cloud. I don't have the numbers in my head. By using compression in the cloud and deduplication, it's something that definitely reduces all the data, probably by more than 20%. That is in comparison to using native cloud source storage solutions.

In terms of our company's cloud costs, we're still seeing about the same amount of money spent. However, it's shifting towards the OpEx part and that gives us the flexibility to scale up and down versus the investment that you have to do upfront in the beginning. It's the shift that we're interested in rather than the total amount at the moment. In the future, we might expect that the cost of the cloud solution will drop. Therefore in the future, we may also see the total costs go down.

We have DR and we once had a problem with electricity and the data moved to the other side of the DR and the user and I didn't know about it. ONTAP has avoided this from occurring in the future.

We tried to use EFS, for example, but one of the cons of EFS was that the performance was degraded once we had a lot of files and very large storage. It took it a while to handle everything. Also, backing up was harder and we needed a third-party. With NetApp it's much easier. Performance is very good and there was no need to change our environments, our speeds, or our automation because we have NetApps on-prem as well. When you have 100,000 files on smaller volumes, or you have bigger volumes with millions of files, it's almost impossible to work with EFS. With NetApp we didn't even feel it. It's all flowing really well.

An example of how ONTAP is improving our organization is through back-up and restore, as well as offsite replication capability. We utilize SnapMirror very heavily on our sites and then also to replicate it offsite to other sites in our organization to make sure that we have very fast local restores if necessary. As well as offsite replication for disaster recovery capabilities as we have certain events that impact our facilities from that perspective.

We use ONTAP for a number of mission-critical applications. Some that specifically run some of our facilities. I'm in the energy industry and we had a certain scenario earlier this year that one of our systems went down and after a few hours I had to start having the conversation with some of the other supervisors if we couldn't get the system back online. However, NetApp support was able to get the system back online with us without having to do an RMA for another device. Support really helped bail us out in that situation of getting the system back online and not having to shut our facility down.

ONTAP has allowed us to keep cost down in the storage environment based upon the deduplication and how we're utilizing it to replicate from a number of different sites and centralize some of our offsite replication capabilities.

By creating snapshots and a multi-cloud dictionary, the solution doesn't have to replicate all the data. The dictionary can point to some of the data on another site and create a correspondence between sites. It's going to lower the storage cost. For example, it saves my clients between 50 and 60 percent.

We save money using CVO because there is a data-tiering concept. There are algorithms that make sure that data which is frequently accessed is kept on the faster disks, and data which is less frequently accessed is stored in a cold tier. Deduplication and compression also provide storage efficiency and savings..

We use it to replicate between data centers. It is for our DR site as well. We use it to create redundancy.

We do on-prem S3 for StorageGRID. The on-prem infrastructure is cheap. It works just the same. It's S3, so it works very well as far as integration and things that use S3 in our environment.

This isn't an isolated solution. We must have NetApp to support our faster access on a file protocol. We found the same solution on Azure is just as helpful when compared to the on-premise solution.

The solution provides us unified storage, no matter what kind of data we have. If we take a normal storage account in the public cloud, then it may not be active in terms of identity level. However, using NetApp, we can leverage the identity management control integrating with our AD. From there, we can gain the computer user's access and maintain the user side entity for who is accessing what.

We are using Linux and eventually, we are going to use SnapMirror. So far, we have seen benefits from using this solution. When we started this process there were some very specific goals about log and files being stored in a single static device. This is achieved with a RAM solution. We are also able to integrate with the cloud, which is another goal we achieved. The solution has also saved us on costs, of course. We calculated that we are saving $1,000,000 across three years.

The consistency of storage management across clouds has effected our storage operations. Essentially, one of the benefits of open NetApp is that ONTAP is pretty much the operating system for any mirrored device, so it doesn't matter if it is in the cloud or on-premises, or whether you use other NetApp products, you pretty much have a safe interface with ONTAP. We like that.

One of our goals is to unify file our block file services into a single storage device. At the same time, we want to replicate on-site services to the cloud. That's also a benefit for us because that way we can move it to the cloud if we need to.

The solution’s unified file and block-storage access across our infrastructure is invaluable. Without it, we can't do what we do.

The consistency of storage management across clouds affects our storage operations by making everybody go to object-based storage, which is not a bad thing. I don't care what cloud provider that you use, they all are based upon what AWS comes out with, which is their S3 object-based storage. NetApp is doing that with with StorageGRID, and that's why we have one and a half petabytes of StorageGRID now, because we have developers and they all want to use object-based storage. Everybody likes puts and gets, but I still prefer traditional NFS.

For the daily activities, we needed the faster storage, faster throughpt, etc. That is why we started using SSDs in certain areas which made the application faster.

The solution's high-availability features are cost-effective for us because we are able to use the cloud benefits to reduce the cost of DR. For example, if we have it in one region, we can copy the data to another region. They keep it powered off and then they power it on for a few minutes, copy the data, send the data again, and shut it down again. That reduces the costs by approximately 80 percent.

Similarly, the data protection provided by the solution's disaster recovery technology is cost-effective and simple.

We're using Cloud Manager to automate some of the management. We use it for bringing the DR environment up and down as well as for scheduling data synchronization between different regions, worldwide. It's almost impossible to do that manually. Compared to an engineer doing it manually, it's about 90 percent faster. That's specifically for this kind of operation. In reality, the automation is enabling such capabilities. It's not actually reducing the time taken. If it didn't exist, we would never do it. That's even better than saving time.

Overall, NetApp has standardized and certified file services, both on-prem and in the cloud, corporate-wide. In addition, by using the automation, it has provided us cost-effective DR and management. In the cloud it has enabled us to provide tailor-made storage solutions for each of our cloud customers. The storage efficiency has reduced our storage footprint because we are offloading all the data to the storage account. So it has reduced the cost of corporate storage. And the data-tiering has also saved us money.

Nos permite sincronizar los métodos de sincronización, basados ​​en la plataforma B2B, para agregarlos correctamente a las listas de correo electrónico del cliente. Nos proporciona calidad y seguridad al mismo tiempo, utilizando estrategias tecnológicas avanzadas. Los resultados son sorprendentes en términos de funcionalidad y defensa contra terceros. 

This solution has helped us because it is easy to use. The ability to find things in the GUI and being able to restore things has been really simple for us.

The Snapshot copies have helped increase our application development speed, especially in testing because we can blow things up and restore it really quickly. Speed to market is where it really helps.

In terms of the consistency of storage management across clouds, this is something that is critical to us because we have several locations. Each of those locations has the infrastructure in place, including some that are overseas. It has become more and more critical for us to manage those things centrally.

In our case, using this solution has not helped to reduce our data footprint in the cloud. If anything, it's growing.

This tool allows working with clean and safe servers. We made a complement and therefore we made progress in optimizing each launch platform in a matter of days.

Our customer is a large organization that has just merged with several other organizations, so they have a lot going on. It was important for them that the time to market was very short, so they needed to deploy fast and get it set up with minimal impact to the business and their IT staff.

Our customer does not use the inline encryption using SnapMirror.

This business is only using file access and no block access. NetApp provides much of their file access across their infrastructure, so this being a DR solution allowed them to have the tertiary copy.

They use Snapshots and I believe they use clones, as well, but I do not have any specific data.

Currently, they are only using AWS, but they certainly are looking at alternatives to save money.

The data footprint in the cloud has expanded since the implementation.

Using NetApp CVO has definitely reduced our customer's overall spend. However, I think that their cloud costs have probably gone up a little bit.

They do not make use of the functionality to move data between hyperscalers and their on-premises environment.

We use this solution's Snapshot copies as part of our data management and data protection strategy. We store these on serial volumes in a public cloud.

The inline encryption using SnapMirror has helped us to address concerns over data security in the cloud. Our enterprise data is private and is protected, but it is still available for our business.