We migrate the databases and keep on-premises and cloud data volumes in sync.
It was an easy sell since it's the same product. We use NetApp on the local storage devices a lot, so it was simple for storage admins. They are very familiar with the product.
The local libraries from NetApp to NetApp are good. This way, we don't have to put the middleman in between to do the transition or conversion.
The NetApp Cloud Volume Services for AWS has been helping migrate workloads onto the cloud. We did migrate a couple of native applications into AWS using this, and it was helpful.
In terms of the integration with AWS native services, I did not configure it by myself. There was another team who did it. That said, I presume they didn't run into any issues, which is why we are using it.
While the solution did not help us reduce the amount of storage, it allowed us to have data replicated across on-premises and in the cloud, so that we have a backup in DR. While it did not reduce the footprint, it helped DR expansion. It increased redundancy.
Since deploying the product, we have not been affected by ransomware or other external threats.
I didn't use the solution in detail to really call for more options. One of the recommended products was this solution. The storage admin that I usually work with prefers this solution. That said, upgrades are always welcome.
We'd like the solution to be less expensive and offer lower latency.
We've used the solution for less than a year.
I'm sure the stability is good. That's why it's there and why we are using it. I haven't had any outages or bad experiences so far.
The scalability is very good. It can grow based on our needs, and it's growing fast.
The support is good. That's why my storage admin likes it. I don't usually do data connect, however, the team that I usually work with is the one who creates the support tickets. They usually get the answers very fast.
We did not use a different solution previously.
We had a POC with the native AWS functions or providers. However, we ended up going with this. We did so due to the fact that the storage admin was familiar with the product and the company, and he preferred that we have an on-premises cloud to manage it within one UI.
We did not migrate from Dell to AWS.
I did not help with the implementation. I came after the initial discussion, and the POC was done. My understanding was that it was straightforward in terms of data migration. Complexity was within the data itself, not in the migration.
It has not helped us save on costs.
I don't deal with the pricing. There is a separate procurement team and licensing team who manage that.
I haven't seen any new investments into the product, however, I'm sure the organization has and that is why they implemented it.
We did not evaluate other options. Somebody recommended this solution, and we implemented based on that.
We do not use NetApp AFF or any other NetApp cloud services.
I'd rate the solution nine out of ten.