Use the rmrcrelationship command to delete an existing remote copy relationship.


rmrcrelationship [ -force ] { rc_rel_id | rc_rel_name }


(Optional) Specifies that the relationship must be deleted even if it results in the secondary volume that contains inconsistent data. This parameter applies only to active-active relationships or Global Mirror relationships that use multi cycling mode.
rc_rel_id | rc_rel_name
(Required) Specifies the ID or the name of the relationship.


This command deletes the relationship that is specified. Deleting a relationship removes the logical relationship between the two volumes but it does not affect the volumes themselves.

If the relationship is disconnected at the time that the command is issued, the relationship is only deleted on the system where the command is being run. When the systems reconnect, the relationship is automatically deleted on the other system. Alternatively, if the systems are disconnected and if you still want to remove the relationship on both systems, you can issue the rmrcrelationship command independently on both of the systems.

If a relationship is active-active or is a Global Mirror relationship that uses multicycling mode, and you attempt to delete the relationship without enabling access first, specifying rmrcrelationship might fail with an error because the relationship does not currently have a fully consistent secondary volume. Specifying -force overrides this test. This is not the default behavior, and you can quiesce and delete the relationship in order to use the secondary volume's data immediately. If the map is still performing the background copy to migrate data from the change volume to the secondary volume, the changed volume and associated FlashCopy mappings remain defined when rmrcrelationship completes. The FlashCopy mappings are deleted after the background copy completes, and the change volume becomes unusable again.

If you delete an inconsistent relationship, the secondary volume becomes accessible even though it is still inconsistent. This case is the only one in which Metro Mirror, Global Mirror, or HyperSwap does not inhibit access to inconsistent data.

An invocation example

rmrcrelationship rccopy1

The resulting output:

No feedback