Recovering the P-VOL (other than DP-VOL) (pair status: PAIR)

Global Active Device for VSP One Block

Version
10.5.x
Audience
anonymous
Part Number
MK-23VSP1B011-10
ft:lastEdition
2026-05-04

The following figure shows the failure area and recovery when a pair is suspended due to a P-VOL failure and the P-VOL is not a DP-VOL.

For details about storage system support (models, firmware) for volumes other than DP-VOLs, see Requirements and restrictions.

Note: In this example no consistency group is specified.


  1. Delete the redundant path (logical path) to the volume that cannot be accessed from the server.
    1. Using the multi-path software, identify the volume that cannot be accessed.
    2. Confirm whether the volume (P-VOL) is blocked.
      raidcom get ldev -ldev_id 0x2222 -IH0
      (snip)
      STS : BLK
      (snip)

      For a blocked volume, BLK is indicated in the STS column.

    3. Using the multi-path software, delete the redundant path to the volume that cannot be accessed from the server.

    Go to the next step even if the redundant path cannot be deleted.

  2. Delete the pair.
    1. From the secondary storage system, delete the pair specifying the actual LDEV ID of the S-VOL.
      pairsplit -g oraHA -R -d dev1 -IH1
      Note: To delete the pair specifying the S-VOL, use the -R option of the pairsplit command. Specify the actual LDEV ID (device name) of the S-VOL in the -d option.
    2. Confirm that the pair is deleted.
      pairdisplay -g oraHA -fxce -IH1Group 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.SMPL ---- ------, ----- ----- - - - - - - - -/-
      oraHA dev1(R) (CL1-A-0, 0, 0)811111 2222.SMPL ---- ------, ----- ----- - - - - - - - -/-
  3. Remove the failure. The following example shows recovery from a volume failure.
    1. Recover the P-VOL.
    2. Display the status of the P-VOL to confirm that the pool volume has been recovered.
      raidcom get ldev -ldev_id 0x2222 -IH0
      (snip)
      STS : NML
      (snip)

      For a normal volume, NML is indicated in the STS column.

  4. If the volume cannot be recovered, follow the procedure below to re-create the P-VOL:
    1. Check whether VSM auto-configuration is used on the P-VOL. In the command result, if AUTO_VIRTUAL_STORAGE is YES, VSM auto-configuration is used on the P-VOL. if AUTO_VIRTUAL_STORAGE is NO, VSM auto-configuration is not used on the P-VOL.
      raidcom get ldev -ldev_id 0x2222 -key virtual -fx -IH0
      LDEV# VIR_LDEV Serial# V_Serial# V_ID V_NUMBER VOL_TYPE
      VIR_VOL_TYPE SSID VIR_SSID AUTO_VIRTUAL_STORAGE
      2222 2222 911111 911111 RH20ETP 1 OPEN-V-CVS
      - a - NO
    2. At the primary storage system, delete the LU path to the P-VOL.
    3. Delete the P-VOL.

      To delete the P-VOL of a GAD pair created by VSM auto-configuration, specify the virtual information reset (-virtual_info reset) option.

    4. Create a new volume.
    5. Check whether the GAD reserve attribute is assigned to the volume created in step d. If the GAD reserve attribute is not assigned, remove the virtual LDEV ID that is set, and then assign the GAD reserve attribute.
      raidcom unmap resource -ldev_id 0x2222 -virtual_ldev_id 0x2222 -IH0
      raidcom map resource -ldev_id 0x2222 -virtual_ldev_id reserve -IH0
      
    6. Set an LU path to the new volume.
  5. 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.
  6. Re-create the pair.
    1. From the secondary storage system, create the pair specifying the S-VOL's actual LDEV ID.
      paircreate -g oraHA -f never -vl -jq 0 -d dev1 -IH1
      Note: To create the pair specifying the S-VOL, specify the actual LDEV ID (device name) of the S-VOL in the -d option of the paircreate command.
      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.
    2. Confirm that the P-VOL and S-VOL pair statuses have 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
  7. Using the multi-path software, add a redundant path from the server to the S-VOL (P-VOL before the failure).
  8. Using the multi-path software, resume I/O from the server to the S-VOL (P-VOL before the failure).
    Note: I/O from the server might resume automatically.
  9. Reverse the P-VOL and the S-VOL if necessary.