Hello, friends. I have two clusters who once had SnapMirror relationships, but we're breaking up the band. I deleted the SnapMirror relationships, vserver peers, and cluster peers on the destination side but failed to do anything like that on the source side. Now there's cluster peer relationship and several stale SnapMirror relationships visible on the source side that I can't delete.
Attempting to delete the cluster peer results in "Nope: A Snapmirror destination exists in this cluster."
"snapmirror list-destinations" on the source cluster results in no entries
"snapmirror show" on the source cluster shows a few stale entries where the destination path is on the old destination cluster in paths that no longer exist on the destination cluster.
No snapmirror commands on the source cluster work when trying to affect the stale destination paths on the destination cluster
Thankfully some network connectivity still exists, because I was able to recreate the cluster peer relationship. The destination vserver on the destination cluster has since been deleted, however, so further commands to "snapmirror release" on the source cluster still fail because it can't find the destination vserver.
Anyway, that's all quite a lot. Really the goal here is to delete (forcibly, if necessary) the cluster peer relationship. Any ideas to get rid of these stale dependencies?
Darn the luck, it didn't work. I was able to recreate the SVM peer relationship, recreate DP volumes, re-establish and initialize the relationship, and then delete-and-release properly, but there's still an artifact of that relationship on the source cluster. I might have to reach out to support after all.