topic Re: Moved Volumes - now Snapmirrors? in ONTAP Discussions

Moved Volumes - now Snapmirrors?

NETPAGA12 — Thu, 05 Jun 2025 06:26:46 GMT

Hello, we moved a volume over to another Netapp. What do we do with the Snapmirror that is now showing 'Broken' which used to be in place?

Delete and reimage, then resync? Or edit existing relationship?

Snapmirror command was used to move volumes over so that relationship needs to be removed as well...?

Re: Moved Volumes - now Snapmirrors?

scottgelb — Mon, 21 May 2012 18:43:06 GMT

If you don't need to replicate back, or to a tertiary site then you can delete the snapmirror snapshots and that will remove the broken entry. You also should edit the snapmirror.conf entries to remove the schedule. Be careful though in case you need to resync back or forward of if another 3rd site where there is dr or other replication.

Re: Moved Volumes - now Snapmirrors?

NETPAGA12 — Mon, 21 May 2012 19:10:43 GMT

What I do need to do is for the moved volume is to replicate that back to the DR site where it was formerly replicating before the move.

Re: Moved Volumes - now Snapmirrors?

scottgelb — Mon, 21 May 2012 19:19:03 GMT

Snap list to check there is a common snapshot between the two systems. If yes the snapmirror resync on the target. If not you have to re initialize.

Sent from my iPhone 4S

Re: Moved Volumes - now Snapmirrors?

VKALVEMULA — Mon, 21 May 2012 19:25:17 GMT

did you try snapmirror resync command ?

Re: Moved Volumes - now Snapmirrors?

NETPAGA12 — Mon, 21 May 2012 20:13:30 GMT

thanks for your help.

There looks to be a common snapshot ...448

I can resync that and go from there?

Re: Moved Volumes - now Snapmirrors?

scottgelb — Mon, 21 May 2012 20:18:06 GMT

yes..be careful which side your resync though...the target will snaprestore back to that snapshot then roll forward from the source.

Re: Moved Volumes - now Snapmirrors?

NETPAGA12 — Mon, 21 May 2012 20:20:24 GMT

soo, I want to resync from the destination, correct?

Re: Moved Volumes - now Snapmirrors?

scottgelb — Mon, 21 May 2012 20:22:21 GMT

Correct...the destination being the system that will revert back to the snapshot then match the source after update (losing all changes since the break)

Re: Moved Volumes - now Snapmirrors?

NETPAGA12 — Mon, 21 May 2012 21:09:55 GMT

I tried and got this:

Cannot specify a snapshot to transfer when snapmirroring an entire volume.

Re: Moved Volumes - now Snapmirrors?

scottgelb — Mon, 21 May 2012 21:12:36 GMT

Just resync and it will fin the common snap. Use -S source fas:volname

Sent from my iPhone 4S

Re: Moved Volumes - now Snapmirrors?

NETPAGA12 — Tue, 22 May 2012 18:59:34 GMT

Hi, I tried this:

snapmirror resync -n -s sourcedestination:sourcevol destsource:destinationtvol

and got this error: Cannot specify a snapshot to transfer when snapmirroring an entire volume.

Is there something else I should be doing?

Re: Moved Volumes - now Snapmirrors?

aborzenkov — Tue, 22 May 2012 19:12:31 GMT

Capital `S' (-S) for source, not small `s'.

Re: Moved Volumes - now Snapmirrors?

NETPAGA12 — Thu, 24 May 2012 15:24:24 GMT

From advice, we opted to create a new snapmirror relation on another aggr.

I removed the snapmirror relationship along w/ any snapshots that had existed on source/destination.

The Snapmirrored volume on the destination that we don't need anymore is safe to delete now?

Re: Moved Volumes - now Snapmirrors?

NETPAGA12 — Thu, 24 May 2012 18:22:39 GMT

From advice, we opted to create a new snapmirror relation on another aggr.

I removed the snapmirror relationship along w/ any snapshots that had existed on source/destination.

The Snapmirrored volume on the destination that we don't need anymore is safe to delete now?