My usual use cases for NetApp SnapMirror are primarily for business continuity reasons, allowing me to offer customers the chance to fail back services to another data center, from Milan to Rome and vice versa, or from Milan to London, or from London to Dublin, for instance. It supports very long distances since it's asynchronous, not synchronous, so any latency is allowed.
Owner - Sales Manager / IT Enterprise Architect at a tech services company with 11-50 employees
Reseller
Top 5
May 16, 2024
NetApp SnapMirror is one of the best solutions for replicating more than 200 machines because it's a hardware-driven product that doesn't consume any CPU cycles from the server farm. In our company, we replicate directly from the storage component. The solution works excellently in large environments. If you compare NetApp SnapMirror with other software solutions such as Veeam, NetApp SnapMirror is ten times easier to use. Using the solution, an exact copy of a disc can be created between two sides. With NetApp SnapMirror, you don't have to deal with any type of software components as the machine being replicated is unaware of the replication process, so any agents are not used. The replication process using the solution occurs on a very low level.
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.
Sr. Manager - System Analyst (Datacenter Infrastructure) at Sohar International
Real User
Sep 13, 2022
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.
Solution Architect at a tech services company with 51-200 employees
Real User
Oct 21, 2019
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.
Senior Application Engineer Presales Support at a wholesaler/distributor with 10,001+ employees
Reseller
Oct 2, 2019
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.
Senior Infrastructure Architect at Proact It Norge As
Real User
Sep 15, 2019
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.
Sr. Manager - System Analyst (Datacenter Infrastructure) at Bank Sohar
Real User
Sep 11, 2019
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.
NetApp SnapMirror technology provides fast, efficient data replication and disaster recovery (DR) for your critical data. Use a single solution across all NetApp storage arrays and protocols. SnapMirror technology works with any application, in both virtual and traditional environments, and in multiple configurations, including hybrid cloud.
My usual use cases for NetApp SnapMirror are primarily for business continuity reasons, allowing me to offer customers the chance to fail back services to another data center, from Milan to Rome and vice versa, or from Milan to London, or from London to Dublin, for instance. It supports very long distances since it's asynchronous, not synchronous, so any latency is allowed.
Our primary use cases for the solution include data replication and backup across our infrastructure.
NetApp SnapMirror is one of the best solutions for replicating more than 200 machines because it's a hardware-driven product that doesn't consume any CPU cycles from the server farm. In our company, we replicate directly from the storage component. The solution works excellently in large environments. If you compare NetApp SnapMirror with other software solutions such as Veeam, NetApp SnapMirror is ten times easier to use. Using the solution, an exact copy of a disc can be created between two sides. With NetApp SnapMirror, you don't have to deal with any type of software components as the machine being replicated is unaware of the replication process, so any agents are not used. The replication process using the solution occurs on a very low level.
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.
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.
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.
The primary use case of this solution is as a storage device. The deployment model we are using is on a private cloud.
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 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.
We primarily use the solution for the infrastructure and for backup replication.
I use the on-prem deployment model for this solution.
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.
We primarily use the solution for replicating data in the storage system.
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.