Recovery procedures from a source UR primary site 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 primary site 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 ) PAIR (Mirror (RL))3
Source UR pair PAIR PAIR － (PSUE 2 ) PSUE 1,2 or PAIR 1
Target UR pair4 COPY or PAIR COPY or PAIR COPY or PAIR COPY or PAIR
Notes:
  1. (VSP One B20 series) The pair status depends on the settings of system option modes (SOMs) 448 and 449.

    (VSP One B85) The pair status depends on the settings of advanced system settings No. 5 and No. 6. For VSP 5100 and 5500, the pair status depends on the settings of system option modes (SOMs) 448 and 449.

  2. The status after powering on the source UR primary site.
  3. The pair status assumes that no I/Os have been issued from the servers to the GAD S-VOL. In the configuration in which no volumes are specified for the quorum disk, the pair status becomes PSUE (Block) when I/Os are issued to the GAD S-VOL while the primary site is in the failed status.
  4. The pair status when the target UR pair has been created.

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.

  1. Specify the S-VOL from the source UR secondary site, and then suspend (swap suspend) the UR pair. 
    pairsplit -g oraUR00 -RS -IH2
  2. Start I/Os from the servers to the storage system at the source UR secondary site.
  3. Remove the failure on the storage system at the source UR primary site.
  4. Specify the P-VOL whose virtual LDEV IDs are set from the source UR primary site, and then forcibly delete the GAD pair. 
    pairsplit -g oraHA00 -SFV -IH1
  5. 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.

  6. Confirm that the source UR pair status has changed to PAIR.
  7. Stop I/Os from the servers to the storage system at the source UR secondary site.
  8. Specify the S-VOL from the source UR primary site, and then suspend (swap suspend) the UR pair. 
    pairsplit -g oraUR00 -RS -IH1
  9. Resume I/Os from the servers to the storage system at the source UR primary site.
  10. Specify the S-VOL from the source UR primary site, and then resynchronize (swap resync) the UR pair. 
    pairresync -g oraUR00 -swaps -IH1
  11. Confirm that the source UR pair status has changed to PAIR.
  12. From the target UR primary site, delete the target UR pair. 
    pairsplit -g oraUR01 -S -IH3
  13. Specify the S-VOL whose virtual LDEV IDs are deleted from the target UR primary site, and then forcibly delete the GAD pair. 
    pairsplit -g oraHA00 -RF -IH3
  14. Create the GAD pair from the source UR primary site. 
    paircreate -g oraHA00 -f never -vl -jq 0 -IH1
  15. Confirm that the GAD pair status has changed to PAIR.
  16. Create the UR pair from the target UR primary site.