Recovering paths, secondary to primary storage system (pair status: PAIR when a volume is set for the quorum disk)

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

The following figure shows the failure area and recovery in a configuration with a volume set for the quorum disk when a pair is suspended due to path failure from the secondary storage system to the primary storage system.



  1. Reconnect the physical path or reconfigure the SAN to recover the path from the secondary storage system to the primary storage system.

    After the path between the storage systems is recovered, the remote path is either automatically recovered or a manual recovery might be required. To verify the remote path status and perform any recommended action, see Troubleshooting related to remote path status. If the remote path failure persists even after following the recommended action, contact customer support.

  2. 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.
  3. Resynchronize the pair.
    1. Confirm that the S-VOL I/O mode is Local.
      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 SSWS 
      NEVER ,  100  2222 -   -   0  -  -            -       - L/L
      oraHA   dev1(R)     (CL1-A-0, 0,   0)811111  2222.P-VOL PSUE 
      NEVER ,  100  4444 -   -   0  -  -            -       - B/B
    2. At the secondary storage system, resynchronize the pair.
      pairresync -g oraHA -swaps -IH1

      The volume on the primary storage system changes to an S-VOL, and the volume on the secondary storage system changes to a P-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.

    3. Confirm that the P-VOL and S-VOL pair statuses change 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.S-VOL PAIR 
      NEVER ,  100  4444 -   -   0  -  -            -       - L/M
      oraHA   dev1(R)     (CL1-C-0, 0,   0)822222  4444.P-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.P-VOL PAIR 
      NEVER ,  100  2222 -   -   0  -  -            -       - L/M
      oraHA   dev1(R)     (CL1-A-0, 0,   0)811111  2222.S-VOL PAIR 
      NEVER ,  100  4444 -   -   0  -  -            -       - L/M
  4. Using the multi-path software, resume I/O to the S-VOL (P-VOL before the failure).

    I/O from the server might resume automatically.

  5. Reverse the P-VOL and the S-VOL if necessary.