stoprcconsistgrp

Edit online

This command can also be used to enable write access to the secondary volumes in the group if the group is in a consistent state.

Syntax

Parameters

-access: (Optional) Allows write access to consistent secondary volumes in the consistency group.
rc_consist_group_id | rc_consist_group_name: (Required) Specifies the ID or the name of the consistency group to stop all processing for.

Description

This command applies to a consistency group. You can issue this command to stop processing on a consistency group that is copying from primary volumes to secondary volumes.

Note: You cannot stop a consistency group by using the -access parameter for a relationship if the primary and secondary volume are different sizes.

If the consistency group is in an inconsistent state, all copy operations stop and do not resume until you issue the startrcconsistgrp command. When a consistency group is in a consistent state (consistent_stopped, consistent_synchronized, consistent_copying, or consistent_disconnected), you can issue the access parameter with the stoprcconsistgrp command to enable write access to the secondary volumes within that group. For a consistency group in the consistent_synchronized state, this command causes a consistency freeze.

The consistent_copying state is a consistent state. A consistency group in this state changes to the consistent_stopped state if it receives a stoprcconsistgrp command. 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 and after the command completes the secondary volume can serve host read and write I/O operations.

If you specify stoprcconsistgrp -access for a consistency group in a consistent_copying state the last consistent image on all the relationships in that group is restored. This process starts a FlashCopy® mapping with the secondary change volume for the secondary volume in each relationship, which might cause the command to fail.

The relationship's data is from a different point in time than the consistency group's data if:

The consistency group is in a consistent_copying state
You add a relationship to the group after the state became consistent_copying

Therefore, the relationship and consistency group are not mutually consistent, and attempting to stop and enable access to the consistency group results in an error. To fix this, let a background copy complete so the consistency group becomes consistent_synchronized) or remove the inconsistent relationship from the consistency group before you enable access. If you stop the consistency group without the -access parameter, the consistency group becomes consistent_stopped but the secondary change volumes continue to retain a consistent image.

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.

It might be necessary to process I/O before the reverse FlashCopy map can be triggered, causing the enable access command to time out. In this case, the relationship delays changing 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 are revealed to the host, and a logical unit number (LUN) inventory changed unit attention is raised to report their availability.

This table shows consistency group initial and final states:

Table 1. stoprcconsistgrp 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`.
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/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`.

An invocation example

stoprcconsistgrp rccopy1

The resulting output:

No feedback