Recovery procedures from the target UR primary site GAD S-VOL failure (LDEV blockade) that occurs after data migration is complete “during migration”

Global Active Device for VSP One Block
Version
10.5.x
Audience
anonymous
Part Number
MK-23VSP1B011-10
ft:lastEdition
2026-05-04

The target UR primary site GAD S-VOL failure (LDEV blockade) that occurs after data migration is complete "during migration"

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)) PSUE (Local)2 (PSUE (Block)2
Source UR pair PAIR PAIR PAIR PAIR
Target UR pair1 COPY or PAIR COPY or PAIR PSUE3 PSUE3
Notes:
  1. The pair status when a target UR pair has been created.
  2. The pair status when a pair that uses the volumes on which a failure occurred accepts the I/Os from the servers. The other pair statuses are the same as those before failure.
  3. The UR pair status when a GAD 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, you must only retry the migration operations for the failed volumes because I/Os from the servers and remote copy operations continue at the source UR site even after the failure occurs. Restore the target UR primary site, and then recreate the GAD pair and the target UR pair.



  1. Delete the target UR pair that uses the failed volume. 
    pairsplit -g oraUR01 -d dev20 -S -IH3
  2. Delete the GAD pair that uses the failed volume. 
    pairsplit -g oraHA00 -d dev10 -S -IH1
  3. Remove the failure on the GAD S-VOL at the target UR primary site, and then recover the S-VOL (Format the S-VOL if the formatting is required for the recovery).
  4. Recreate a GAD pair that uses the volume recovered from the failure. 
    paircreate -g oraHA00   -d dev10 -f never -vl -jq 0 -IH1
  5. Confirm that the GAD pair status has changed to PAIR.
  6. If the target UR pair is suspended, resynchronize the UR pair. 
    pairresync -g oraUR01 -IH3
  7. Recreate a target UR pair that uses the volume recovered from the failure. 
    paircreate -g oraUR01 -d dev20 -f async -vl -jp 0 -js 0 -IH3