Everybody in our company relies on SnapMirror, as everyone uses it to transfer data. We use it 24/7 and 365 days a year, running continuously to synchronize data. It is mostly used for data replication, data recovery, and data transfer. It helps to transfer the data to other sites and from the storage system to different files. If there is downtime or some emergency at the data center, NetApp SnapMirror will recover all of the mirrored data to another site. 

We have two sites, a primary site and a disaster recovery site. The files used in the primary site need continuous replication to DR in case recovery is needed either for test DR drill or in the event we need to failover any applications or databases to our disaster recovery site. I'm a senior manager system analyst and we are customers of NetApp. Our company is based in Oman. 

We use the solution for backup and DR purposes. We use it on-prem and cloud, but mainly on-prem since we have the physical storage. We have the AFF and Flash series from NetApp. Our cloud is used for the destination of SnapMirror. In our current infrastructure, we are running SnapMirror worldwide from the source. SnapMirror replicates itself into the cloud.

One customer used it to migrate their data. I checked SnapMirror after a few hours, and it was working properly. 

We use SnapMirror for monitoring backups. We use the product if we have a primary site and want to create a secondary site for a backup.

Our customers use the solution to move data from one site to another. They do it every day. There’s a schedule for SnapMirror. It is for data protection.

There are multiple cases that we use for backup mainly, but also to migrate volumes for secondary backup.  

The solution is used for storage. Customers use the product if they want to have virtual machines run on shared storage. It provides users with ease of access to their files and folders remotely.

We are a solution provider, and this is one of the products that we resell to our clients.

I am a presales engineer and have experience with this solution. I teach my customers how to use it.

This solution provides safety and data protection for my customers. 

The deployment model depends on the customer. However, in Poland, the private cloud model is the most popular. Many are moving to a hybrid-cloud, but the public cloud is still not very popular.

The main reason we use NetApp SnapMirror is to try to have a disaster recovery site. We want to have the possibility to do disaster recovery to failover to another site when there is a problem, but also to failover to another site during maintenance, for instance. So if the customers are going to do some maintenance, they can failover to the other site and keep on running. 

NAS Filer with quick recovery features within same site or across DR site. Being a unified storage, it is used as a Block (SAN) storage as well with pretty decent performance.

Our primary use case of this solution is as a system integrator, we don't use it for ourselves because we don't have such a big infrastructure. We don't have, for example, the disaster recovery requirements but our customers generally use the replication for disaster recovery. Another way to use SnapMirror is to replicate, to use it to copy the backups. For example, you make a copy of the data on your main storage and you just move it to backup storage, which is not really disaster recovery, you can say that it's a technical backup solution.

Some customers will use it as an asynchronous replication which is a good idea. Synchronous replication is not always ideal because you are not sure about the pertinency of data. In the case of snapshots, asynchronous SnapMirror, when we are making snapshots and then replicating the snapshots, you can be sure that at least the second snapshot is good and concurrent. That's the difference between synchronous and asynchronous.

This solution is a storage replication software, embedded in storage filing that takes a snapshot copy and transfers it to a different location and a different Net Application.

The deployment model we are using is on-premises.

We primarily use the solution for replicating data in the storage system.

We primarily use the solution for the infrastructure and for backup replication.

The primary use case of this solution is as a storage device. 

The deployment model we are using is on a private cloud.

I use the on-prem deployment model for this solution.