Clustered Data ONTAP is a multi-tenant system, the cluster and SVM peering system supports this. The cluster administrator configures peering relationships at the cluster level, followed by SVM administrators configuring them at the SVM layer. With this division of labor, a tenant who has multiple SVMs on multiple clusters can manage their own peering and configuring the SnapMirrors, while the cluster admin is only responsible for ensuring that the underlying infrastructure (intercluster links, cluster peers, etc.) is configured.
To change a destination from read-only to read-write you'll need to do the following from the cluster shell:
# from the destination, stop future transfers of the snapmirror
snapmirror quiesce -destination-path vserver:volume
# break the relationship, making the destination read-write
snapmirror break -destination-path vserver:volume
# junction the volume
volume mount -vserver vserver -volume volume -junction-path "/volume"
# at this point the clients would need to mount the volume from the
# new source, the destination SVM NFS LIF(s)
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
When a source volume becomes unavailable for read/write access, you can perform a volume-level disaster recovery failover and resynchronization from OnCommand System Manager. This functionality is available from the Protection page of the destination Vserver. For further info see the below links: