stoprcrelationship

The stoprcrelationship command stops 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 VDisk.

Syntax

Read syntax diagramSkip visual syntax diagram
>>- svctask -- -- stoprcrelationship -- --+-----------+-- ------>
                                          '- -access -'      

>--+- rc_rel_id ---+-------------------------------------------><
   '- rc_rel_name -'   

Parameters

-access
(Optional) Specifies that the system allow write access to a consistent secondary VDisk.
rc_rel_id | rc_rel_name
(Required) Specifies the ID or the name of the relationship to stop all processing for.

Description

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 VDisks.

If the relationship is in an inconsistent state, any copy operation stops and does not resume until you issue a svctask 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, or consistent_disconnected state – you can use the access parameter to enable write access to the secondary virtual disk. Table 1 provides consistency group initial and final states.

Table 1. stoprcrelationship consistency group states
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.
idling idling Remains in idling state whether access is specified or not.
idling_disconnected unchanged If specified without access, the relationship/group remains in idling_disconnected state. If the clusters reconnect, the relationship/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/group moves to idling_disconnected.

An invocation example

svctask stoprcrelationship rccopy1

The resulting output

No feedback
Library | Support | Terms of use | Feedback
© Copyright IBM Corporation 2003, 2009. All Rights Reserved.