YKDELETE (dissolves copy pairs)

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

This command dissolves copy pairs for the specified copy group and changes the volume status to the SIMPLEX status.

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

If the copy pair to be dissolved is in the SIMPLEX status or any status that cannot be dissolved because of the attributes in the copy group structure, the command returns a non-zero return code.

Request body format

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

Parameters specified in the request body

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

Specify the IDs 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. If the UR ATTIME suspend time has been set for the target copy group, execute the YKSUSPND command with the CANCEL parameter specified to cancel the UR ATTIME suspend time before you execute the YKDELETE command with the DEVN parameter specified.

SELECT({ALL|COND})

Specify the method used to select the copy pairs that are to be affected by this command. The default is ALL.

ALL

All the copy pairs in the copy group are affected by the command. Note that if the DEVN parameter is specified, the copy pair specified for the parameter becomes the execution target of the command.

COND

Only pairs with certain volume statuses are affected by the command. If copy pairs that are not affected by the command are included in the copy group, the processing terminates with the return code 4. For details on the copy pairs that are affected by the command, see the table "Copy pair statuses for which commands with SELECT(COND) specified are subject to processing" in the Hitachi Business Continuity Manager User Guide.

Notes

• Do not execute the YKDELETE command during planned outage operation (when switching the P-VOL and S-VOL). To dissolve the copy pair, switch the P-VOL and S-VOL again, return the P-VOL to the primary site (restore normal operation), and then dissolve the copy pair.

• When operating the copy groups of a copy pair that was deleted by specifying the DEVN parameter, for the time that the copy pair is being synchronized, make sure that you specify the SELECT(COND) parameter.

• For EXCTG, if you execute the YKDELETE command and then the YKQUERY command to obtain the copy pair status, the YKZ296E message sometimes appears when the dissolving of the copy pair is detected at a different time from the dissolving of EXCTG, but this does not mean that an error has occurred. For this reason, for EXCTG, we recommend that you execute the YKDELETE command and then the YKEWAIT GOTO(SIMPLEX) command, wait until the copy pair status changes to SIMPLEX, and then execute the YKQUERY command.

• 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 YKDELETE 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, or YKSUSPND.

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 YKDELETE command.

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