Recovery procedures from a source UR primary site failure that occurs before deleting a source UR pair "after migration is complete"

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 following table 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 (Block)3
Source UR pair PAIR PAIR － (PSUE 2 ) PSUE 1,2 or PAIR 1
Target UR pair PAIR PAIR PAIR 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. 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.

You must perform this failure recovery operations in the target UR environment because the system environmental migration for the UR remote copy function is complete. Perform the pair operations so that the S-VOL at the target UR secondary site can accept I/Os from the servers to recover the I/Os because the GAD S-VOL cannot accept the I/Os if a failure occurs.

You must perform this failure recovery operations in the target UR environment, and then remove the source UR environment.

Use the following procedure to recover the remote copy function from a failure that occurs at the source UR primary site.

  1. Specify the S-VOL from the target UR secondary site, and then suspend (swap suspend) the UR pair. 
    pairsplit -g oraUR01 -RS -IH4
  2. Start I/Os from the servers to the storage system at the target UR secondary site.
  3. Specify the S-VOL whose virtual LDEV IDs are set from the target UR primary site, and then forcibly delete the GAD pair. 
    pairsplit -g oraHA00 -RFV -IH3
  4. Specify the S-VOL from the target UR secondary site, and then resynchronize (swap resync) the UR pair. 
    pairresync -g oraUR01 -swaps -IH4

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

  5. Confirm that the target UR pair status has changed to PAIR.
  6. Stop I/Os from the servers to the storage system at the target UR secondary site.
  7. Specify the S-VOL from the target UR primary site, and then suspend (swap suspend) the UR pair. 
    pairsplit -g oraUR01 -RS -IH3
  8. Resume I/Os from the servers to the storage system at the target UR primary site.
  9. Specify the S-VOL from the target UR primary site, and then resynchronize (swap resync) the UR pair. 
    pairresync -g oraUR01 -swaps -IH3
    The volume of the target UR pair at the primary site has changed to the P-VOL and the volume at the secondary site has changed to S-VOL.