Recovering from a source UR S-VOL failure (LDEV failure) that occurs after data migration is complete “during migration”

Global Active Device for VSP One Block

Version
10.5.x
File Size
25537 KB
Audience
anonymous
Part Number
MK-23VSP1B011-11
ft:lastEdition
2026-06-23

The table below shows the changes in the pair status before and after a failure.

Pair type Pair status before failure Pair status after failure
P-VOL S-VOL P-VOL S-VOL
GAD pair PAIR

(Mirror (RL))

PAIR

(Mirror (RL))

PAIR

(Mirror (RL))

PAIR

(Mirror (RL))

Source UR pair PAIR PAIR PSUE2 PSUE2
Target UR pair1 COPY or PAIR COPY or PAIR COPY or PAIR COPY or PAIR
Note:
  1. The pair status when a target UR pair has been created.
  2. The pair status when a pair that uses the volume on which a failure occurred accepts the I/Os from the servers. If the error level of the UR pair is set to Mirror, all UR pairs belonging to the mirror are in this pair status.

When recovering from this failure, use the existing source UR environment for the system recovery. No pair operations are required until the recovery from the failure because I/Os from the servers continue at the source UR site even after the failure occurs. Therefore, you can proceed with the UR environmental migration. For more information about the procedures followed when proceeding to the completion of the migration, see Recovering from a source UR S-VOL failure (LDEV failure) that occurs before deleting the source UR pairs "after migration is complete".

The following describes the procedure for recovering to the status before a failure occurs.



  1. Delete the source UR pair that uses the failed volume.
    pairsplit -g oraUR00 -d dev00 -S -IH1
  2. Remove the failure on the UR S-VOL at the source UR secondary site, and then recover the S-VOL (Format the S-VOL if the formatting is required for the recovery).
  3. Delete the target UR pair that shares the same volumes with a GAD pair sharing the same volumes with a source UR pair that uses the failed volume.
    pairsplit -g oraUR01 -d dev20 -S -IH3
  4. Suspend the GAD pair sharing the same volumes with a source UR pair that uses the failed volume by specifying the P-VOL, and then delete the pair.
    pairsplit -g oraHA00 -d dev10 -IH1
    pairsplit -g oraHA00 -d dev10 -S -IH1
    
  5. Resynchronize the source UR pair if the source UR pair is suspended.
    pairresync -g oraUR00 -IH1
  6. From the source UR primary site, recreate a source UR pair that uses the volume recovered from the failure.
    paircreate -g oraUR00 -d dev00 -f async -vl -jp 0 -js 0 -IH1
  7. Confirm that the UR pair status has changed to PAIR.
  8. From the source UR primary site, recreate the GAD pair deleted in step 4.
    paircreate -g oraHA00 -d dev10 -f never -vl -jp 0 -IH1
  9. Confirm that the GAD pair status has changed to PAIR.
  10. From the target UR primary site, recreate the target UR pair deleted in step 3.
    paircreate -g oraUR01 -d dev20 -f async -vl -jp 0 -js 0 -IH3