Recovery procedure for GAD pair suspension due to other failures

Global Active Device for VSP One Block

Version

10.5.x

File Size

25537 KB

Audience

anonymous

Part Number

MK-23VSP1B011-11

ft:lastEdition

2026-06-23

A GAD pair might be suspended due to a failure other than those described in this chapter. Use the following procedure to recover a suspended pair from other types of failure.

If you are not able to restore the GAD volumes using this procedure, contact customer support.

Recover from the failure.
1. Verify that a failure, such as a suspended GAD pair, has occurred, for example, by checking for SIMs issued by the primary or secondary storage system.
2. When a failure has occurred, identify the failure and perform troubleshooting according to the failure type to remove the cause of the failure.
Confirm the quorum disk status. If the quorum disk is blocked, recover from the blockade. If you do not set a volume for the quorum disk, you can skip this step.

Resynchronize the GAD pair.

Check the I/O mode of the P-VOL and the S-VOL of the suspended GAD pair.

pairdisplay -g oraHA -fxce -IH0
Group   PairVol(L/R) (Port#,TID, LU),Seq#,LDEV#.P/S,Status,
Fence,   %,P-LDEV# M CTG JID AP EM       E-Seq# E-LDEV# R/W
oraHA   dev1(L)     (CL1-A-0, 0,   0)811111  2222.P-VOL PSUE 
NEVER ,  100  4444 -   -   0  -  -            -       - L/L
oraHA   dev1(R)     (CL1-C-0, 0,   0)822222  4444.S-VOL PSUE 
NEVER ,  100  2222 -   -   0  -  -            -       - B/B

pairdisplay -g oraHA -fxce -IH1
Group   PairVol(L/R) (Port#,TID, LU),Seq#,LDEV#.P/S,Status,
Fence,   %,P-LDEV# M CTG JID AP EM       E-Seq# E-LDEV# R/W
oraHA   dev1(L)     (CL1-C-0, 0,   0)822222  4444.S-VOL PSUE 
NEVER ,  100  2222 -   -   0  -  -            -       - B/B
oraHA   dev1(R)     (CL1-A-0, 0,   0)811111  2222.P-VOL PSUE 
NEVER ,  100  4444 -   -   0  -  -            -       - L/L

If the I/O mode of the P-VOL is Local, resynchronize the GAD pair at the primary storage system.
```
pairresync -g oraHA -IH0
```
If the I/O mode of the S-VOL is Local, resynchronize the GAD pair at the secondary storage system.
```
pairresync -g oraHA -swaps -IH1
```
The volume in the primary storage system changes to an S-VOL, and the volume in the secondary storage system changes to a P-VOL.

Confirm that the pair status of the P-VOL and the S-VOL of the GAD pair has changed to PAIR (Mirror (RL)).

pairdisplay -g oraHA -fxce -IH0
Group   PairVol(L/R) (Port#,TID, LU),Seq#,LDEV#.P/S,Status,
Fence,   %,P-LDEV# M CTG JID AP EM       E-Seq# E-LDEV# R/W
oraHA   dev1(L)     (CL1-A-0, 0,   0)811111  2222.P-VOL PAIR 
NEVER ,  100  4444 -   -   0  -  -            -       - L/M
oraHA   dev1(R)     (CL1-C-0, 0,   0)822222  4444.S-VOL PAIR 
NEVER ,  100  2222 -   -   0  -  -            -       - L/M

pairdisplay -g oraHA -fxce -IH1
Group   PairVol(L/R) (Port#,TID, LU),Seq#,LDEV#.P/S,Status,
Fence,   %,P-LDEV# M CTG JID AP EM       E-Seq# E-LDEV# R/W
oraHA   dev1(L)     (CL1-C-0, 0,   0)822222  4444.S-VOL PAIR 
NEVER ,  100  2222 -   -   0  -  -            -       - L/M
oraHA   dev1(R)     (CL1-A-0, 0,   0)811111  2222.P-VOL PAIR 
NEVER ,  100  4444 -   -   0  -  -            -       - L/M

Using the multi-path software, resume I/O to the S-VOL.
If necessary, reverse the P-VOL and the S-VOL.
If a failure occurs after the one volume capacity of a GAD pair can be expanded, the creation, resync, swap resync, and horctakeover operations of the GAD pair cannot be performed because the capacity of both the volumes is not the same. Make sure to expand the other volume capacity so that the capacity of both the volumes is the same, and then retry the operation.