In correct steps while deleting the smas relationship

Open
#2,138 0 comments 0 reactions 1 assignee View on GitHub

@netapp-lenida is already working on this.

Since Sep 19, 2026.

Assessment

This issue has not been assessed yet.

Description

Page URL

https://docs.netapp.com/us-en/ontap/snapmirror-active-sync/remove-configuration-task.html

Page title

Remove an ONTAP SnapMirror active sync configuration

Summary
  • Before deleting a SnapMirror active sync SAN relationship, all LUNs that are part of the relationship on the destination cluster must be unmapped.

  • If a destination LUN is mapped through a replicated igroup, the igroup replication must first be removed from the source cluster before the LUN mapping can be deleted on the destination cluster.
    SiteB::> igroup show -igroup <igroup_name> -vserver <vserver_name> -fields replication-peer

  • If the igroup is replicated, remove the replication-peer association from the source cluster:
    SiteA::> igroup modify -vserver <svm_name> -igroup <igroup_name> -replication-peer "-"

  • Verify that the igroup is no longer replicated:
    SiteB::> igroup show -igroup <igroup_name> -vserver <vserver_name> -fields replication-peer

  • Delete the destination-side LUN mapping:
  • SiteB::> lun mapping delete -vserver <svm_name> -igroup <igroup_name> -path <lun_path>
  • If there are no additional LUNs mapped to the igroup, delete the igroup
  • After the LUNs are unmapped and the host is rescanned, the SCSI target notifies the hosts that the LUN inventory has changed. The existing LUNs on the zero RTO secondary volumes change to reflect a new identity after the SnapMirror active sync relationship is deleted. Hosts discover the secondary volume LUNs as new LUNs that have no relationship to the source volume LUNs.
  • The secondary volumes remain DP volumes after the relationship is deleted. You can issue the snapmirror break command to convert them to read/write.
  • Deleting the relationship is not allowed in the failed-over state when the relationship is not reversed.

Steps
From the secondary cluster, remove the SnapMirror active sync consistency group relationship between the source endpoint and destination endpoint:

destination::>snapmirror delete -destination-path vs1_dst:/cg/cg_dst

From the primary cluster, release the consistency group relationship and the snapshots created for the relationship:

source::>snapmirror release -destination-path vs1_dst:/cg/cg_dst

Perform a host rescan to update the LUN inventory.

Beginning with ONTAP 9.10.1, deleting the SnapMirror relationship does not delete the consistency group. If you want to delete the consistency group, you must use System Manager or the ONTAP REST API. See Delete a consistency group for more information.

Public issues must not contain sensitive information
  • This issue contains no sensitive information.
Dominant language
No language data
Stars
39
Forks
87
Avg merge
27m
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NetAppDocs/ontap

All issues in NetAppDocs/ontap

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.