Recovery procedures from a source UR P-VOL 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

A source UR P-VOL failure 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 (Block) 2 SSWS (Local)2
Source UR pair PAIR PAIR PSUE 3 PSUE 3
Target UR pair1 COPY or PAIR COPY or PAIR COPY or PAIR COPY or PAIR
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 the failure.
  3. The pair status when a pair that uses the volumes 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 Mirror are in this pair status.

When recovering from this failure, use the existing source UR environment for the system recovery. You must perform the pair operations so that the S-VOL at the source UR secondary site can accept I/Os from the server to continue the I/Os. After that, recover the primary site, and then restore the configuration using the S-VOL data.



The steps to the target UR pair can be skipped if there are no target UR pairs.

  1. Stop I/Os from the servers to the journal to which the failed pair belongs on the source UR primary storage system.
  2. Specify the S-VOL from the source UR secondary site, and then suspend (swap suspend) the UR pair. 
    pairsplit -g oraUR00 -RS -IH2
  3. Start I/Os from the servers to the storage system at the source UR secondary site.
  4. Delete the UR pair on which the P-VOL failure occurred at the source UR primary site. 
    pairsplit -g oraUR00 -d dev00 -S -IH1
  5. Specify the P-VOL whose virtual LDEV IDs are set, and then forcibly delete the GAD pair on which the P-VOL failure occurred at the source UR primary site. 
    pairsplit -g oraHA00 -SFV -d dev10 -IH1
  6. Delete the target UR pair sharing the same volumes with the GAD pair on which the P-VOL failure occurred. 
    pairsplit -g oraUR01 -d dev20 -S -IH3
  7. Specify the S-VOL whose virtual LDEV IDs are deleted, and then forcibly delete the GAD pair on which the P-VOL failure occurred at the source UR primary site. 
    pairsplit -g oraHA00 -RF -d dev10 -IH3
  8. Remove the P-VOL failure at the source UR primary site, and then recover the P-VOL (Format the P-VOL if the formatting is required for the recovery).
  9. Specify the P-VOL, and then suspend the GAD pair sharing the same volumes with a different UR pair that uses the journal to which the failed UR pair belongs. 
    pairsplit -g oraHA00 -IH1
  10. Specify the P-VOL from the target UR primary site, and then suspend the UR pair. 
    pairsplit -g oraUR01 -IH3
  11. Specify the S-VOL from the source UR secondary site, and then resynchronize (swap resync) the UR pair. 
    pairresync -g oraUR00 -swaps -IH2

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

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

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

  18. Confirm that the source UR pair status has changed to PAIR.
  19. Resynchronize the GAD pair from the source UR primary site. 
    pairresync -g oraHA00 -IH1
  20. Create a GAD pair that uses the volume recovered from the failure. 
    paircreate -g oraHA00 -f never -vl -jp 0 -d dev10 -IH1
  21. Confirm that all GAD pair statuses have changed to PAIR.
  22. Resynchronize the UR pair from the target UR primary site. 
    pairresync -g oraUR01 -IH3
  23. Create a target UR pair sharing the same volumes with the GAD pair on which the failure occurred. 
    paircreate -g oraUR01 -d dev20 -f async -vl -jp 0 -js 0 -IH3