Starting and stopping Metro Mirror, Global Mirror, or active-active consistency-group copy processes by using the CLI

You can use the command-line interface (CLI) to start and stop Metro Mirror, Global Mirror, or active-active consistency-group copy processes.

About this task

Complete these steps to start and stop Metro Mirror, Global Mirror, or active-active consistency-group copy processes.

Note: Avoid concurrent service actions that affect the same remote-copy relationship or consistency group in multiple clustered systems. Where possible, run command-line interface (CLI) commands, including scripted CLI commands, on each clustered system sequentially. Running commands sequentially ensures that no single relationship or consistency group is processing concurrent commands from multiple sources.

Procedure

To start a Metro Mirror, Global Mirror, or active-active consistency-group copy process, set the direction of copy if it is undefined and optionally mark the secondary volumes of the consistency group as clean. Run the startrcconsistgrp command.
For example, enter the following command:
```
startrcconsistgrp rc_consist_group_id
```
where rc_consist_group_id is the ID of the consistency group to start processing.
Note: If you are starting an active-active consistency group, all relationships in the group must be in the idling state for the consistency group to start.
When you restart a Metro Mirror, Global Mirror, or an active-active consistency-group copy process, you can determine the previous copy direction from the previous_primary attribute that is displayed by using the lsrcconsistgrp command.
To stop the copy process for a Metro Mirror or Global Mirror consistency group, run the stoprcconsistgrp command.
For example, enter the following command:
```
stoprcconsistgrp rc_consist_group_id 
```
Where rc_consist_group_id is the ID of the consistency group that you want to stop processing.

If the group is in a consistent state, you can also use this command to enable write access to the secondary volumes in the group.
To stop the copy process for an active-active consistency group, the following conditions must be met:
- The -access parameter is specified.
- The state of the relationships in the consistency group is consistent_copying.
- The status of the relationships in the consistency group is primary_offline.
For example, enter the following command:
```
stoprcconsistgrp rc_consist_group_id -access 
```
Where rc_rel_id is the ID of the active-active consistency group that you want to stop. The -access parameter gives hosts read or write access to a volume in an active-active relationship that contains an older but a consistent image that can be used in a disaster recovery scenario.
To restart a Metro Mirror or a Global Mirror consistency-group copy process in the idling state, run the startrcconsistgrp command. You must use the -primary parameter to specify the copy direction if the consistency-group copy process was stopped using the -access parameter. To determine the copy direction before the consistency-group copy process was stopped, run the lsrcconsistgrp command. The previous_primary field indicates which consistency-group was the primary (source) consistency-group for the copy process before the consistency-group copy process was stopped. When the consistency-group copy process is in the idling state, the value is either master or aux. For active-active consistency-group copy processes which are part of a HyperSwap volume the previous_primary field is not used and the value is blank.
For example, to restart a consistency-group copy process that has been stopped using the -access parameter, enter the following command:
```
startrcconsistgrp -primary rc_copy_direction rc_consist_group_id
```
Where rc_copy_direction is the value for the primary (source) consistency-group and rc_consist_group_id is the ID of the consistency group to start processing.