Hi,
What is the preferred method of performing a Snapmirror Reverse Resync after a DR scenario where we want to keep the data that has been written to the volumes?
I have two Clusters - Cluster1 in the Primary DC and Cluster2 in the Secondary DC where under normal circumstances, the volumes on Cluster2 are the Snapmirror Destinations.
In a DR scenario all Snapmirror volumes in Cluster2 are now Broken-Off, read /write and we have written data to the volumes in Cluster2.
I've read the following process on https://www.flackbox.com/netapp-snapmirror-data-protection (possibly the old way to do it) where the snapmirror is deleted from Cluster2, recreated on Cluster1 with Cluster2 as the source and Cluster1 as the destination and then resynced. Once the sync is done, the Snapmirror is deleted from Cluster1 and then recreated back on Cluster2, resulting in Cluster2 now being the Snapmirror destination.
Is this no longer the recommended method to follow?
The second process that I have read is once the Snapmirror is broken-off on Cluster2, a Snapmirror resync is performed on Cluster1 making Cluster2 the Source and Cluster1 the destination.
The process is discussed here: https://vmstorageguy.wordpress.com/2018/01/07/how-to-netapp-ontap-reverse-snapmirror-cdot/
Is this now the recommended way to run the reverse resync?
I am aware that the resync can be done in System Manager, but will be performing via the CLI.
Thanks,
Ben
