Recovering from a target UR S-VOL failure (LDEV blockade) that occurs after data migration is complete "during migration"

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²	COPY or PAIR	COPY or PAIR	PSUE¹	PSUE¹
Note: The pair status when a pair that uses the volumes on which a failure occurred is in the process of initial copy or 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. The pair status when a target UR pair has been created.

When recovering from this failure, use the existing source UR environment for the system recovery. The following describes the procedure for recovering to the status before a failure occurs.

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
```
From the target UR primary site, re-create a target UR pair that uses the volume recovered from the failure.
```
paircreate -g oraUR01 -d dev20 -f async -vl -jp 0 -js 0 -IH3
```