Recovering from a target UR S-VOL failure (LDEV blockade) that occurs before deleting the source UR pairs "after migration is complete"

Global Active Device for VSP One Block

Version

10.5.x

Audience

anonymous

Part Number

MK-23VSP1B011-10

ft:lastEdition

2026-05-04

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
Pair type	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	PAIR	PAIR
Target UR pair	PAIR	PAIR	PSUE¹	PSUE¹
The pair status when a pair that uses the volume on which a failure occurred accepts the I/Os from the servers. If the error level of the UR pair is set to Mirror, all UR pairs belonging to the mirror are in this pair status.

When recovering from this failure, you must perform this failure recovery operations in the target UR site, and then remove the source UR environment because the system environmental migration for the remote copy function is complete.

Delete the target UR pair that uses the failed volume.
```
pairsplit -g oraUR01 -d dev20 -S -IH3
```
Remove the failure on the UR S-VOL at the target UR secondary site, and then recover the S-VOL (Format the S-VOL if the formatting is required for the recovery).
Resynchronize the target UR pair if the target UR pair is suspended.
```
pairresync -g oraUR01 -IH3
```
Recreate a target UR pair that previously used the failed volume.
```
paircreate -g oraUR01 -d dev20 -f async -vl -jp 0 -js 0 -IH3
```
Remove the source UR environment in accordance with the procedure in Removing the source environment.