Moving Data from One Cluster to Another

[NEO-BAHAMUT]

Hi All

I've got two NetApp clusters. "ClusterA" and "ClusterB". Both are running ONTAP 9.11.1P10.

"ClusterA" has an SVM that contains a volume that has thousands of Shares attached to it (Which is also around 15TB in size). We are planning on Decommissioning "ClusterA" but before we do that we need to move the data over to "ClusterB". 

What is the best, easiest and safest / most reliable method for us to do this? We need to migrate the SVM from ClusterA to ClusterB but also keep everything in the exact same state. Is there a way?

Just to also mention (i'm not sure if this matters), there is a cluster peer between both clusters.

Thanks

[JPick]

I would look at SVM-DR.  Here is the documentation: https://docs.netapp.com/us-en/ontap/data-protection/snapmirror-svm-replication-concept.html

-Thx

[wareer]

You can use SnapMirror to create a data protection relationship between SVMs. In this type of data protection relationship, all or part of the SVM's configuration, from NFS exports and SMB shares to RBAC, is replicated, as well as the data in the volumes that the SVM owns.

Before you can protect your data by replicating it to a remote cluster for data backup and disaster recovery purposes, you should create a cluster peer relationship between the local and remote cluster.
https://docs.netapp.com/zh-cn/ontap/data-protection/replicate-entire-svm-config-task.html 

[cedric_renauld · Accepted solution]

Hello

To keep all identities, like IP, share, Names and SSID from AD windows, you must do a SVM-DR, with the "preserve identiry" option.

and at the cut over time you have a little workflow to change definitively the DR SVM to a production SVM.

See this post :

https://community.netapp.com/t5/ONTAP-Discussions/How-to-migrate-a-Snapmirror-SVM-DR-source-SVM-to-a-new-cluster/m-p/450768

And this docs :

https://docs.netapp.com/us-en/ontap/data-protection/make-svm-destination-volumes-writeable-task.html

[ak2000]

You can use svm-migrate as well instead of svm-dr. 

https://docs.netapp.com/us-en/ontap/svm-migrate/migrate-svm-task.html#migrate-an-ontap-svm-with-automatic-cutover-enabled

[ethelreiz]

Given your setup and requirement to keep the SVM, shares, permissions, and overall state intact, the best and most reliable approach is to use SVM SnapMirror (SVM-DR) between ClusterA and ClusterB. Since the clusters are already peered and running the same ONTAP version, this method will replicate the entire SVM configuration and data consistently, allow for incremental updates, and support a clean, planned cutover with minimal downtime before decommissioning ClusterA. It’s a well-tested, supported approach for exactly this use case and avoids the complexity and risk of manual volume or share recreation. For smoother planning and reference, it’s also worth visiting or downloading bstation to track migration steps, documentation, or operational notes in one place during the transition.