Complete this task to resynchronize the volumes, B volumes to A
volumes. This is the second step in the failback recovery process
that allows production to be returned to your A site.
Before you can do this task, you must ensure that you have created
paths from Site B to Site A between the specific LSSs.
This task requires the use of the
failbackpprc command.
Processing this command resynchronizes the volumes in the following manner
depending on the volume state:
- If a volume at Site A is in simplex state, all of the data for that volume
is sent from Site B to Site A.
- If a volume at Site A is in full-duplex or suspended state and without
changed tracks, only the modified data on the volume at Site B is sent to
the volume at Site A.
- If a volume at Site A is in a suspended state but has tracks that have
been modified, the volume at Site B will discover which tracks were modified
at any site and send both the tracks that were changed on Site A and the tracks
that were marked at Site B from Site A to Site B.
Perform the following step to resynchronize your volumes. The
example commands displayed in this task are shown in two formats. The first
format shows the type of information the command requires. The second format
provides the command with declared values for the variables.
Note: This task
does not affect normal operations. All your operations remain at the remote
site (Site B). This task is just part of the preparation you need to make
to transfer operations back to Site A after it has been repaired.
Issue the failbackpprc command to resynchronize your volumes.
Enter the failbackpprc command at the dscli command prompt with the
following parameters and variables: dscli>failbackpprc -dev storage_image_ID -remotedev storage_image_ID
-type gcp source_volume_ID:target_volume_ID
Example
dscli>failbackpprc -dev IBM.1750–68FA150 -remotedev IBM.1750–68FA120
-type gcp 1000:1000
Notes: - The -dev parameter specifies the ID of your source storage unit.
At this point in time, your source is the Site B storage unit.
- The -remotedev parameter specifies the ID of the target storage
unit. At this point in time, the remote storage unit is your Site A storage
unit.
- The source_volume_ID:target_volume_ID value has the Site
B volume ID as the source and the Site A volume ID as the target.
After submitting this command for processing, you must track the
progress of the transaction until it completes its first pass. So, querying
for first pass completion is the next step in the failback recovery process.