topic Re: Lingering traces of broken mirrors in ONTAP Discussions https://community.netapp.com/t5/ONTAP-Discussions/Lingering-traces-of-broken-mirrors/m-p/44662#M10453 <HTML><HEAD></HEAD><BODY><P>Have you removed base snapshots left by snapmirror?</P></BODY></HTML> Thu, 22 Mar 2012 03:08:32 GMT aborzenkov 2012-03-22T03:08:32Z Lingering traces of broken mirrors https://community.netapp.com/t5/ONTAP-Discussions/Lingering-traces-of-broken-mirrors/m-p/44658#M10452 <HTML><HEAD></HEAD><BODY><P>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.</P><P></P><P>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?</P><P></P><P>In case it matters, the situation was a bit more complex - we had a cascade of mirrors, eg,</P><P></P><P>&nbsp; filers1:volname1 -&gt; filer2:volname2 -&gt; filer1:volname3</P><P></P><P>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.</P><P></P><P>None of this affects any production work, but it'd be nice to have the status correctly reflect the change.</P></BODY></HTML> Thu, 05 Jun 2025 06:31:33 GMT https://community.netapp.com/t5/ONTAP-Discussions/Lingering-traces-of-broken-mirrors/m-p/44658#M10452 steve_simmons 2025-06-05T06:31:33Z Re: Lingering traces of broken mirrors https://community.netapp.com/t5/ONTAP-Discussions/Lingering-traces-of-broken-mirrors/m-p/44662#M10453 <HTML><HEAD></HEAD><BODY><P>Have you removed base snapshots left by snapmirror?</P></BODY></HTML> Thu, 22 Mar 2012 03:08:32 GMT https://community.netapp.com/t5/ONTAP-Discussions/Lingering-traces-of-broken-mirrors/m-p/44662#M10453 aborzenkov 2012-03-22T03:08:32Z