Starting a background copy of a FlashCopy relationship

Complete this task to create a FlashCopy® volume pair that allows data to be copied from the source volume to the target volume.

When you issue a FlashCopy command without using the nocp parameter, the FlashCopy relationship is established but it is put in a queue for background copying. The exact time that the background copying starts for the specific relationship depends on the number of FlashCopy relationships that have already begun, or are waiting to begin, background copying. When the background copy starts, the state of that FlashCopy volume pair is displayed as "background copy running".

A background copy causes all data on the source volume to be physically copied to the target volume. After a FlashCopy pair is established, an automatic withdrawal of the FlashCopy relationship occurs when all source tracks have been physically copied to the target volume (unless the FlashCopy relationship was designated as persistent by using the persist parameter when it was established).
Note: The amount of time that the actual physical copy can take depends on the amount of data that is copied and other activities that are occurring on the storage unit. You can monitor when the copy completes by issuing the lsflash command to check the status information for each FlashCopy relationship.

Perform the following steps to create FlashCopy relationships with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format is an example command with declared values for the variables.

  1. Issue the mkflash command without the nocp parameter to create FlashCopy relationships that allow data to be copied from the source volume to the target volume. Enter the mkflash command at the dscli command prompt with the following parameters and variables:

    dscli>mkflash -dev storage_image_ID sourcevolumeID:targetvolumeID

    Example
    dscli>mkflash -dev IBM.1750-68FA150 0001:0004
    Note: Specify the storage unit for the -dev storage_image_ID parameter. This parameter is required if you do not specify a fully qualified ID for the source and target volumes and you do not specify a value for the devidvariable in your profile file.

    A confirmation message is issued for each successful FlashCopy pair that is created.

  2. Issue the lsflash command to check the status information for each FlashCopy relationship. A detailed report (when you use the -l parameter) is displayed for each FlashCopy relationship. Enter the lsflash command at the dscli command prompt with the following parameters and variables:

    dscli>lsflash -dev storage_image_ID -l SourceVolumeID:TargetVolumeID.

    Example

    dscli>lsflash -dev IBM.1750-68FA150  -l 0100:0100

    Use the -l parameter to provide a more detailed report about the FlashCopy relationships.

Library | Support | Terms of use | Feedback
© Copyright IBM Corporation 2004, 2007. All Rights Reserved.