Due to the physical path failure between the storage systems at the primary site of the temporary GAD pair used for migration (source GAD primary site) and the secondary site of the temporary GAD pair used for migration (target GAD primary site), the pair status of the temporary GAD pair used for migration 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 the recovery procedure for when the temporary GAD pair used for migration is in different status, see Disaster recovery when migrating GAD pairs.
If the pair status of the temporary GAD pair used for migration becomes PSUE(Block) for the P-VOL and SSWS(Local) for the S-VOL due to a physical path failure, the data migration is complete. If this is the case, continue the migration procedure for GAD+UR operations in the target environment.
-
If a physical path failure occurs between the storage systems at the primary
site and secondary site of the temporary GAD pair used for
migration, remove the cause of failure.
The pair status for the temporary GAD pair for migration becomes PSUE(Local) for the P-VOL and PSUE(Block) for the S-VOL.Note: The S-VOL might be in COPY status when a physical path failure occurs. In that case, if you remove the cause of failure, the status changes to PSUE(Block).
-
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.