Preparing to reinstate production at the local site

Edit online

Complete this task to begin the process of returning production to your local site. Just as there was a series of steps in the failover recovery process to your remote site, there are a series of steps that you must take to return production to your local site.

About this task

Returning production to its original implementation is called a failback recovery. After restoring operations at Site A, you can schedule a failback operation to synchronize data and to enable production to resume at your original site, Site A.

This task is initiated when your local site has been repaired and is operational. The first step in returning production to site A is to create Fibre Channel paths between Site B to Site A and between the specific LSSs.

Complete the following steps to create Fibre Channel paths from Site B to Site A and between the specific LSSs. 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 provides the command with values declared for the variables.
Notes:
  1. Before you can establish the paths, you must obtain the worldwide node name that is associated with the remote storage system. In this task your remote storage system is your local storage system (Site A).
  2. You can enter the commands that are described in the steps for a DS8000® model.

Procedure

  1. Issue the lssi command against the Site A storage system to obtain its worldwide node name. A report is displayed that provides the specific information about the Site A storage system. Enter the lssi command at the dscli command prompt with the following parameters and variables:

    dscli> lssi -l storage_image_ID

    Example

    dscli> lssi -l IBM.2107-75FA120

    Record the worldwide node name because it is used in the next step.

  2. Issue the mkpprcpath command to create the Fibre Channel paths from Site B to Site A and between the specific LSSs. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables:

    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-75FA150 -remotedev 
IBM.2107-75FA120 -remotewwnn 12341234000A000A
-srclss IBM.2107-75FA150/00 -tgtlss IBM.2107-75FA120/01 
I1A20:I2A10
    

    Notes: 
      

    1. The -dev parameter specifies the ID of your source storage system. At this point in time,
your source is the Site B storage system.
      2. 


    2. The -remotedev parameter specifies the ID of the secondary storage system. At this point
in time, the remote storage system is your Site A storage system.
      3. 


    3. The -remotewwnn parameter must specify the worldwide node name of the secondary storage
system (Site A at this point in time). If you specify the worldwide node name of the primary storage
system (Site B), the command fails.
      4. 


    4. The -srclss parameter refers to Site B storage system as the source.
      5. 


    5. The -tgtlss parameter specifies the Site A storage system as the target.
      6. 


    6. The source_port_ID:target_port_ID value has the
Site B port ID as the source and the Site A port ID as the target.
      7. 


    

    

    

    3. 




What to do next
After you have established the paths, you are ready to move on to the second step on the
failback recovery process which involves entering the failbackpprc command from the B volume
to the A volume.