Reestablishing remote mirror and copy paths (site A to site B)

Edit online

Complete this task to reestablish the remote mirror and copy paths between site A and site B in preparation for the transfer of operations from the B site to the A site. This is the fourth step in the failback disaster recovery process.

Before you begin

Each of the prior tasks must be competed in sequence in order for this task to succeed.

About this task

This task is like your initial creation of remote mirror and copy paths while setting up your Global Mirror environment, before the disaster occurred.

Create paths so that the logical subsystems (LSSs) are associated with each other. These are the ports that the copy services I/O pass through. It is preferred that they are not the same ports that are used for host I/O. This ensures that there is enough capacity for the data transfer.

Complete the following steps to create remote mirror and copy paths between all Global Mirror source and target pairs and between the master and subordinate storage systems. The example commands in this task are shown in two formats. The first format shows the type of information that is required by the command. The second format provides the command with declared values for the variables.

Procedure

  1. Obtain the worldwide node name of the secondary storage system. This information is needed when you do the next step. Enter the lssi or showsi at the dscli command prompt as follows: 
    dscli> lssi -l
    This is the entire command. No additional variables are needed.

    The showsi command does contain a variable and a command: dscli> showsi storage_image_id -fullid

    Example
    dscli> showsi -fullid IBM.2107-75FA120
    Notes:
    1. Use the lssi command if you want to display a list of all the storage image instances for a storage complex and the status information for each storage image in the list.
    2. Use the showsi command if you want to display the detailed properties of a specific storage system.
    3. Use the -fullid DS CLI command with the showsi command to display fully qualified IDs, which include the storage image ID, for every ID that is displayed in the command output.
    4. Record the worldwide node name for the secondary (target) site B storage system so that you can use it when you enter the mkpprcpath command.
  2. Issue the mkpprcpath command to create the remote mirror and copy paths between all Global Mirror source and target pairs and between the master and subordinate storage systems. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables as follows:

    dscli> mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn -srclss source_LSS_ID -tgtlss target_LSS_ID source_port_ID:target_port_ID

    Example
    dscli> mkpprcpath -dev IBM.2107-75FA120 -remotedev 
IBM.2107-75FA150 -remotewwnn 12341234000A000F
-srclss 00 -tgtlss 01 I1A10:I2A20
    Notes:
    1. The -remotedev parameter specifies the ID of the secondary storage system.
    2. The -remotewwnn parameter must specify the worldwide node name of the secondary storage system. If you make a mistake and specify the worldwide node name of the primary storage system, the command fails.
    3. The shortened version of the -srclss parameter is shown (value = 00) because the example uses the fully qualified -dev storage_image_ID parameter. If the fully qualified -dev parameter is not used, you must use the fully qualified -srclss source_LSS_ID value. For example: -srclss IBM.2107-75FA120/00.
    4. The shortened version of the -tgtlss parameter is shown (value = 01) because the example uses the fully qualified -dev storage_image_ID parameter. If the fully qualified -dev parameter is not used, you must use the fully qualified -tgtlss target_LSS_ID value. For example: -tgtlss IBM.2107-75FA120/01.
    5. The shortened version of the source_port_ID:target_port_ID parameter is shown (value = I1A10:I2A20) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_image_ID parameters. If the fully qualified -dev and -remotedev parameters are not used, you must use the fully qualified source_port_ID:target_port_ID value. For example: IBM.2107-75FA120/I1A10:IBM.2107-75FA150/I2A20 .
      The fully qualified source_port_ID:target_port_ID parameter is positional on your command line. It must be placed after the -tgtlss parameter and value. For example:
      dscli> mkpprcpath -srclss 00 -tgtlss 01
IBM.2107-75FA120/I1A10:IBM.2107-75FA150/I2A20