Use the stoprcrelationship command to stop the copy process for a Metro Mirror or Global Mirror stand-alone relationship. You can also use this command to enable write access to a consistent secondary volume including for an active-active relationship.
The stoprcrelationship command applies to a stand-alone relationship. The command is rejected if it is addressed to a relationship that is part of a consistency group. You can issue this command to stop a relationship that is copying from primary to secondary volumes.
If the relationship is in an inconsistent state, any copy operation stops and does not resume until you issue a startrcrelationship command. For a relationship in the consistent_synchronized state, this command causes a consistency freeze.
When a relationship is in a consistent state – in the consistent_stopped, consistent_synchronized, consistent_copying, or consistent_disconnected state – you can use the access parameter to enable write access to the secondary volume. Table 1 provides consistency group initial and final states.
The consistent_copying state is a consistent state. A relationship in consistent_copying state transitions to consistent_stopped state when you specify stoprcrelationship. Because the secondary change volume holds the consistent image, a stopped consistent_copying relationship might not have its secondary change volume deconfigured. This can be achieved by enabling access or completing synchronization so the secondary disk contains a consistent image. A relationship in consistent_copying or consistent_stopped accepts stoprcrelationship-access transition to idling state.
The consistent image that is present on the change volume is made accessible at the secondary volume. After the command completes, the secondary volume can serve host read and write I/O.
A FlashCopy background copy operation begins to migrate the data for the consistent image from the change volume to the secondary volume. While the background copy operation is in progress, the change volume for the secondary volume remains in use.
The enable access command can time out if there is I/O to process before the reverse FlashCopy map can be triggered. In this case, the relationship delays transitioning to idling until the reverse map starts and write access is available. Read access to the consistent data remains available.
Any remote copy secondary volumes that are mapped to hosts of type hide_secondary are presented to the host if you specify -access. Paths to those volumes appear to the host, and a logical unit number (LUN) inventory changed unit attention is raised to report their availability.
When you enable read or write access for a consistent_copying relationship, specify stoprcrelationship -access to restore a consistent image on the secondary change volume that is using a FlashCopy mapping. (Depending on how long this operation lasts the CLI command might delay.) This process fails if either the secondary volume or secondary change volume are offline. If you stop the relationship without specifying the -access parameter, the relationship becomes consistent_stopped and the secondary change volume is unchanged.
To enable access to a secondary volume that is not consistent, specify rmrcrelationship -force.
| Initial state | Final state | Notes |
|---|---|---|
| inconsistent_stopped | inconsistent_stopped | If access is specified, the command is rejected. |
| inconsistent_copying | inconsistent_stopped | If access is specified, the command is rejected with no effect and the relationship remains in the inconsistent_copying state. |
| consistent_stopped | consistent_stopped | If access is specified, the final state is idling. |
| consistent_synchronized | consistent_stopped | If access is specified, the final state is idling. If access is not specified, the final state is consistent_stopped. |
| consistent_copying | consistent_stopped | If access is specified, the final state is idling. If access is not specified, the final state is consistent_stopped. |
| idling | idling | Remains in idling state whether access is specified or not. |
| idling_disconnected | unchanged | If specified without access, the relationship or group remains in idling_disconnected state. If the clustered systems reconnect, the relationship or group is in either inconsistent_stopped or consistent_stopped state. |
| inconsistent_disconnected | inconsistent_stopped | The command is rejected, with or without the access flag. |
| consistent_disconnected | consistent_stopped | The command is rejected if specified without access. If specified with access, the relationship or group moves to idling_disconnected state. |
stoprcrelationship rccopy1
The resulting output:
No feedback