SnapMirror® from NetApp has enabled dependable and efficient data duplication between storage units. This functionality has been extended with the introduction of Cloud Volume ONTAP, allowing cloud-based devices to be incorporated in a replica topology, substantially simplifying complex installations such as cloud-onboarding of apps or establishing a fog DR (disaster recovery) scenario. More information on how AWS snapshots help secure cloud deployments can be found here. Cloud Volumes ONTAP creates a virtual memory appliance on AWS using Amazon EC2 & Amazon EBS cloud resources. In the same manner that on-premises solutions have been utilized, a Cloud Storage ONTAP instance can operate as the gateway in a SnapMirror relationship. Users can synchronize data from on-premises, from cloud to online, cloud to on-premises, or cloud to cloud, with incremental updates to keep the data synchronized.
SnapMirror’s wide variety of capabilities and its connectivity with the other Storage Volumes ONTAP technologies make it a versatile and robust data replication solution. We’ll look at how NetApp duplication with SnapMirror functions, how to set it up, and the benefits of utilizing SnapMirror to duplicate your data to the AWS cloud. Data Replication with NetApp SnapMirror What is data replication, or does NetApp SnapMirror Reproduction with Amazon Web Services work? The technique of data from one location and duplicating it in another is known as data replication.
SnapMirror uses Cloud Volume ONTAP snaps to control data transfer from one place to another, as the name implies. A complete copy predicated on a snap of the origin volume is copied across to the destination to accomplish a baseline synchronization. The latest update is prepared and contrasted to the base snapshot as data changes at the source. The altered blocks are then duplicated to the target, with the newer picture becoming the new baseline or newest shared snapshot. This makes it possible to repeat the operation and send incremental updates to the destination. The target volume is in an online noticed state whenever a SnapMirror relationship is established, but it is still available.
SnapMirror operates with physical storage blocks rather than files or other logical structures. The target volume is an exact clone of the source volume, including snapshots, quantity settings, etc. If the source volume uses Cloud Containers ONTAP space efficiency capabilities like data compression and deduplication, the duplicated volume will keep similar optimizations. When SnapMirror is used to process large amounts of data to a DR environment, terminating the SnapMirror connection makes the destination disc readable, commonly used to initiate a failover. SnapMirror is smart enough to allow data updated at the backup site to be rapidly resynchronized back to the primary server, should it come back online later, and then for the original data to be restored.
SnapCenter® can be used with SnapMirror to duplicate application consistency snapshots, like those used for database backups. Since Cloud Volumes ONTAP backups are made in conjunction with an application using the base storage, there is a certainty that no I/O operations will produce errors in the snapshot, making them stand out among alternative database replication tools and methodologies. SnapCenter can then instruct SnapMirror to use its consistent snapshot to synchronize all defined destinations after producing it. SnapMirror can also migrate databases to the cloud, including AWS data migration.
What’s the best way to set it up?
Step-by-Step SnapMirror NetApp NetApp Cloud Administrator is a web-based UI for installing Cloud Volume ONTAP to AWS and controlling your NetApp storage system on-premises and in the cloud. It’s simple to set up new SnapMirror relationships using this interface: drag and drop the origin ONTAP system in your ecosystem onto the destination to start the wizard, walking you through the remainder of the process.
The wizard will ask you to select the input and output volume for the current SnapMirror relation and other parameters like maximum download speed so that you can manage the network bandwidth utilized for synchronization. You’ll also need to choose a synchronization schedule, which you may do by selecting “One-time copy.”
Finally, the program will wish to review the configuration & confirm that you want to move forward. The progress of the AWS replicates and data transfer may be checked using the dashboard once the SnapMirror connection has already been formed.
SnapMirror is a powerful feature of Cloud Containers ONTAP that would be both flexible and simple to utilize, as we’ve seen. Whether you’re transferring your production apps to AWS or using Cloud Volume ONTAP for disaster recovery, SnapMirror can help you get your data where it needs to go as quickly as possible—for example, in big lift and shift Aws migrations.
SnapMirror also works well with other Storage Volumes with ONTAP capabilities. For instance, you can offload data straight to Amazon S3 by SnapMirroring data to a target disk in Cloud Containers ONTAP that leverages data tiering. It can be a very price solution for infrequently used systems, including such DR scenarios.
