Breaking SnapMirror relationships
You must break a mirror relationship if a mirror source becomes unavailable and you want client applications to be able to access the data from the mirror destination. After the mirror relationship is broken, the destination volume type changes from DP to RW.
Before you begin
The SnapMirror destination must be in the quiesced state or idle state.
The destination volume must be mounted on the destination
storage virtual machine (SVM) namespace.
About this task
You can use the destination volume to serve data while you repair or replace the source, update the source, and reestablish the original configuration of the systems.
You can break SnapMirror relationships between ONTAP systems and SolidFire storage systems.
If you are break a FlexGroup volume relationship, you must refresh the page to view the updated status of the relationship.
- Click .
- Select the mirror relationship that you want to break.
- Click .
- Select the confirmation check box, and then click Break .
Result
The data protection SnapMirror relationship is broken. The destination volume type changes from data protection (DP) read-only to read/write. The system stores the base Snapshot copy for the data protection mirror relationship for later use.
For an Infinite Volume, a new mirror is created on the volume if the namespace mirror constituent does not already exist. The namespace mirror constituent is required on the destination volume to provide data protection to the namespace constituent.