YKRECVER (dissolves copy pairs from a secondary site)

Applies to TrueCopy, TrueCopy with the HyperSwap attribute, and Universal Replicator.

When copy pair operations from the Primary site are disabled due to failure or other reasons, this command dissolves a copy pair for the specified copy group from the Secondary site.

When you use this command to dissolve a copy pair, the volume on the Secondary site assumes the SIMPLEX status, but the volume on the Primary site takes the SUSPER status. Note, however, that depending on the status of the Primary site, the status of the volumes in the Primary site do not change even after the copy pair is dissolved.

The above site names are for cases when the copy direction of copy pair configuration and the copy direction which is actually recognized on the storage system are the same. For the opposite copy direction, replace the primary site and secondary site with the secondary site and primary site respectively. However, do not dissolve copy pairs during a planned outage.

When dissolving copy pairs in a copy group container with EXCTG ID, if all copy pairs are dissolved from a journal group, that journal group will be deleted from the EXCTG. In addition, if all journal groups are deleted from the EXCTG, the EXCTG data will be deleted.

Request body format

{ "action":"submit",
   "cliname":"YKRECVER",
   "operands":"
     [GROUP(copy-group-ID)]
     [△1DEVN(p-vol-device-number, s-vol-device-number)]
   "
}

Parameters specified in the request body

GROUP(copy-group-ID) ~ <GROUP string>

Specify the ID of the target copy groups that are loaded. If only one copy group is loaded, you can omit this parameter.

DEVN(p-vol-device-number,s-vol-device-number) ~ <4-digit hexadecimal number, 4-digit hexadecimal number>

Specify the device number of the copy pair (P-VOL and S-VOL) to operate.

Notes

• Do not dissolve copy pairs during a planned outage.

• In 4x4x4 Delta Resync configurations, when all copy pairs in EXCTG whose copy direction is from the primary site to the remote site are dissolved, the journal groups whose copy direction is from the local site to the remote site are also dissolved from EXCTG registration.

  For example, if a Delta Resync is executed and then the YKRECVER command is executed when EXCTG is in the HOLD status and the copy direction is from the primary site to the remote site, the journal groups whose status is DUPLEX and copy direction is from the local site to the remote site are dissolved from EXCTG registration. As a result, the YKZ296E message is output if the YKQUERY command is executed to obtain the status of Universal Replicator copy pairs whose copy direction is from the local site to the remote site. In this case, perform either of the following operations to register journal groups in EXCTG for the storage system:

  • Execute the YKMAKE HOLD command for Universal Replicator copy pairs whose copy direction is from the primary site to the remote site.

  • Execute the YKMAKE command with a SELECT(COND) specified for Universal Replicator copy pairs whose copy direction is from the local site to the remote site.

Responses

See Responses returned by YKDELETE, YKMAKE, YKRECVER, YKRESYNC, YKSUSPND, or YKRMTCDV.

Return code

If the CLI command has finished running, the return code of the CLI command is set in the rc key of the response. If an error occurs before the CLI command is run, the BCM Web API server sets the return code.

The following table lists and describes the return codes of the YKRECVER command.

For details about return codes set by the BCM Web API server, see Return codes set by the BCM Web API server.