topic Re: How to convert snapmirror destination into source and source into destination? in ONTAP Discussions

How to convert snapmirror destination into source and source into destination?

rickdallow — Thu, 05 Jun 2025 07:15:59 GMT

We are about to move the NetApp filer hosting (along with other data) a snapmirror source from our primary data center to a remote site. We would like to bring the current snapmirror destination filer to our primary data center, and therefore we would need to convert the snapmirror destination to be the snapmirror source at our primary data center, and convert the former snapmirror source to be the new snapmirror destination at the remote site.

I would appreciate any guidance you folks can provide. As an added complication, this snampmirror relationship may have been created in Protection Manager, so that may require the swapping of source/destination be done within Protection Manager.

AFAIK the license is the same for snapmirror source and destination, so the existing licenses should suffice.

Suggestions on how to achieve this goal either by DFM or PM will be appreciated.

Thanks

Rick

Re: How to convert snapmirror destination into source and source into destination?

adaikkap — Fri, 09 Apr 2010 06:41:08 GMT

Are you using DR Dataset?

Then you can failover.

Delete the dataset.

Reverse the relationship.(you are free to use the filer cli or dfdrm clis of DFM)

Create new dataset and import the reversed relationship in PM.

If its not DR dataset, then.

Delete the dataset.

Reverse the relationship.(you are free to use the filer cli or dfdrm clis of DFM)

Discover them in DFM.

Create new dataset and import the reversed relationship in PM.

Regards

adai

Re: How to convert snapmirror destination into source and source into destination?

BrendonHiggins — Fri, 09 Apr 2010 09:31:23 GMT

We do change the destination twice a year to show our RISK team we can do it. Works fine and we have done it many times over the years. The only problem is if you change the back to quickly. In the past we changed, ran the service for a week then changed back again. We keep 3 weeks of snapshots and WAFL can go 'strange' and start slowing down. The answer is to run in the 2nd site for more than the snapshot retention period, ie 3 weeks or to delete the snapshots created on the 1st filer before failing back to the primary site again.

Hope this helps

Bren