NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

ONTAP Discussions

Lingering traces of broken mirrors

steve_simmons
2,593 Views

I have a snapmirror which has been properly broken off, but traces remain. By properly broken off, we removed the entry from snapmirror.conf, and did a snapmirror quiesce and break on the former target. The target volume was then deleted.

However, if one does a snapmirror status on the original host, the source volume still shows as being mirrored to the target. Any suggestions on how to get rid of that?

In case it matters, the situation was a bit more complex - we had a cascade of mirrors, eg,

  filers1:volname1 -> filer2:volname2 -> filer1:volname3

volname3 was quiesced, broken, and deleted. On filer1, volname3 no longer appears in 'snapmirror status.' On filer2, 'snapmirror status' still shows filer2:volname2 being mirrored to filer1:volname3.

None of this affects any production work, but it'd be nice to have the status correctly reflect the change.

1 REPLY 1

aborzenkov
2,593 Views

Have you removed base snapshots left by snapmirror?

Public