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)) |
PAIR (Mirror (RL)) |
PAIR (Mirror (RL)) |
| Source UR pair | PAIR | PAIR | PAIR1 or PSUE1, 2 | - (PSUE2) |
| Target UR pair3 | COPY or PAIR | COPY or PAIR | COPY or PAIR | COPY or PAIR |
|
Note:
|
||||
When recovering from this failure, use the existing source UR environment for the system recovery. No pair operations are required until the recovery from the failure because I/Os from the servers continue at the source UR site even after the failure occurs. Therefore, you can proceed with the UR environmental migration. For more information about the procedures followed when proceeding to the completion of the migration, see Recovering from a source UR secondary site failure that occurs before deleting the source UR pairs "after migration is complete".
The following describes the procedure for recovering to the status before a failure occurs.
- Remove the failure on the storage system at the source UR secondary site.
- Resynchronize the source UR pair.
- Confirm that the UR pair status has changed to PAIR.