Due to the physical path failure between the storage systems at the source GAD primary site and secondary site, the pair status of the source GAD pair becomes PSUE(Local) for the P-VOL and PSUE(Block) for the S-VOL. This procedure changes the pair status back to the status during migration to the target GAD+UR environment.
For details about recovering from a physical path failure where the pair status of the source GAD pair becomes PSUE(Block) for the P-VOL and SSWS(Local) for the S-VOL, see Disaster recovery when migrating GAD pairs.
-
If a physical path failure occurs between the storage systems at the source
GAD
primary site and secondary site, remove the cause of failure.
The pair status for the P-VOL and S-VOL of the different pairs will be as follows:
- For the source GAD pair: PSUE(Local) for the P-VOL and PSUE(Block) for the S-VOL
- For the temporary GAD pair for migration: The pair status does not change, or changes to PAIR for both P-VOL and S-VOL
Note: For VSP One B85, the status of the source UR delta resync P-VOL in the figure is PSUE. -
Suspend the temporary GAD pair used for migration.
Command example:
pairsplit -g HA20 -IH01
Note: For VSP One B85, the status of the source UR delta resync P-VOL in the figure is PSUE. -
Resynchronize the source GAD pair.
Command example:
pairresync -g HA00 -IH01
Note: For VSP One B85, the status of the source UR delta resync P-VOL in the figure is PSUE. -
Verify that the pair status of the source GAD pair becomes
PAIR.
-
Resume host I/Os to the source GAD secondary site.
-
Resynchronize the temporary GAD pair used for migration.
Command example:
pairresync -g HA20 -IH01
In this configuration, the pair status of the temporary GAD pair used for migration does not change to PAIR and remains COPY.