Recovery procedures from the target UR primary site GAD S-VOL failure (LDEV blockade) that occurs before deleting a source UR pair "after migration is complete"

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 before deleting a source UR pair "after migration is complete"

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)1 (PSUE (Block)1
Source UR pair PAIR PAIR PAIR PAIR
Target UR pair PAIR PAIR PSUE2 PSUE2
Notes:
  1. The pair status when a pair that uses the volume on which a failure occurred accepts the I/Os from the servers. The other pair statuses are the same as those before failure.
  2. The pair status when a UR 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 perform the pair operations so that the S-VOL at the target UR secondary site can accept I/Os from the server to continue the I/Os. Perform this failure recovery operations in the target UR environment, and then remove the source UR environment because the system environmental migration for the remote copy function is complete.

  1. Stop I/Os from servers to the storage system at the target UR primary site.
  2. Specify the S-VOL, and then suspend (swap suspend) the target UR pair. 
    pairsplit -g oraUR01 -RS -IH4
  3. Resume I/Os from servers to the storage system at the target UR secondary site.
  4. Delete the source UR pair by specifying the P-VOL. 
    pairsplit -g oraUR00 -S -IH1
  5. Specify the S-VOL whose virtual LDEV IDs are set, and then forcibly delete the GAD pair. 
    pairsplit -g oraHA00 -RFV -IH3
  6. Specify the P-VOL whose virtual LDEV IDs are deleted, and then forcibly delete the GAD pair. 
    pairsplit -g oraHA00 -SF -IH1
  7. Delete the target UR pair that uses the failed volume. 
    pairsplit -g oraUR01 -d dev20 -S -IH3
  8. Remove the GAD S-VOL failure at the target UR primary site, and then recover the S-VOL (Format the S-VOL if the formatting is required for the recovery).
  9. Resynchronize the target UR pair by specifying the S-VOL. 
    pairresync -g oraUR01 -swaps -IH4

    The volume of the target UR pair at the primary site has changed to S-VOL and the volume at the secondary site has changed to P-VOL.

  10. From the target UR secondary site, create a target UR pair that uses the volume recovered from the failure. 
    paircreate -g oraUR01 -d dev20 -f async -vl -jp 0 -js 0 -IH4
  11. Confirm that the target UR pair status has changed to PAIR.
  12. Stop I/Os from servers to the storage system at the target UR secondary site.
  13. Specify the S-VOL from the target UR primary site, and then suspend (swap suspend) the UR pair. 
    pairsplit -g oraUR01 -RS -IH3
  14. Resume I/Os from servers to the storage system at the target UR primary site.
  15. Specify the S-VOL from the target UR primary site, and then resynchronize (swap resync) the UR pair. 
    pairresync -g oraUR01 -swaps -IH3

    The subsequent sections provide how to remove the source UR environment in accordance with the procedure in Removing the source environment.