Recovering the quorum disk (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

When the GAD status of the pair changes to Suspended, the P-VOL I/O mode changes to Local and the S-VOL I/O mode changes to Block. Server I/O continues on the P-VOL.

(VSP One B20 series) When the GAD status of the pair changes to Quorum disk blocked, the P-VOL I/O mode remains Mirror (RL), and the S-VOL I/O mode changes to Block.
(VSP One B85) When the GAD status of the pair changes to Quorum disk blocked, the P-VOL and S-VOL I/O modes remain Mirror (RL).

Server I/O continues on the P-VOL.

The following figure shows the failure area and recovery when a pair is suspended due to quorum disk failure.

Note: In this example no consistency group is specified.

Note: The following procedure is also used for re-creating the quorum disk when it has been mistakenly reformatted.

Note: Steps 1 and 2 below describe the recovery procedure for an external storage system made by Hitachi, for example, VSP E590. If you are using another vendor's storage system as external storage, follow the vendor's recovery procedure for the storage system. When you complete the recovery procedure for the external storage system, start the following procedure at step 3.

On the external storage system, recover the quorum disk.
1. Block the quorum disk.
2. Format the quorum disk.
  If the quorum disk recovers after formatting, go to step h.
  If the quorum disk does not recover after formatting, continue to step c.
  
  Note: You can recover the quorum disk by replacing its external storage system with a new one while keeping the GAD pair.
3. Confirm the following information about the quorum disk:
  - Vendor
  - Machine name
  
  - Volume properties
  
  - Device ID (if the information is valid)
  
  - Serial number
  
  - SSID
  
  - Product ID
  
  - LBA capacity (the capacity must be larger than the quorum disk before the failure occurred)
  
  - CVS attribute
  
  For details about confirming this information, see the Universal Volume Manager User Guide.
  
  For details about confirming the CVS attribute, see the following table.
4. Delete the LU path to the quorum disk.
5. Delete the volume that is used as the quorum disk.
6. Create a new volume.
  For the LDEV ID, set the same value as the LDEV ID of the quorum disk that has been used since before the failure occurred. If you cannot set the same value, go to step 3.
  Also set the same values for the following information as the values that were used before the failure occurred. If you cannot set the same value, go to step 3.
  
  - Vendor
  
  - Machine name
  
  - Volume properties
  
  - Device ID (if the information is valid)
  
  - Serial number
  
  - SSID
  
  - Product ID
  
  - LBA capacity (the capacity must be larger than the quorum disk before the failure occurred)
  
  - CVS attribute
  
  For details about confirming this information, see the Universal Volume Manager User Guide. For details about confirming the CVS attribute, see the following tables.
7. Set an LU path to the new volume.
  For the LU number, set the same value as the LU number of the quorum disk that was used since before the failure occurred. If you cannot set the same value, go to step 3.
8. Reconnect the external storage system or the quorum disk to the primary and secondary storage systems.

If the GAD status of the pair is Quorum disk blocked: The pair changes to the Mirrored status automatically.

If the GAD status of the pair is Suspended: Resynchronize the pair as follows.

Confirm that the P-VOL I/O mode is Local.

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

On the primary storage system, resynchronize the pair.
```
pairresync -g oraHA -IH0
```
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.

Confirm that the P-VOL and S-VOL pair status has changed to PAIR (Mirror (RL)). If so, go to step 4.

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

Re-create the pairs.

On the primary storage system, delete all pairs that use the quorum disk where the failure occurred.
```
pairsplit -g oraHA -S -d dev1 -IH0
```

Confirm that the pairs were deleted.

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.SMPL  ---- ------,  ----- -----   -   -   -   -  -        -      -       -/-
oraHA   dev1(R)      (CL1-C-0, 0,   0)822222  4444.SMPL  ---- ------,  ----- -----   -   -   -   -  -        -      -       -/-

On the primary and secondary storage systems, delete the quorum disk.
On the primary and secondary storage systems, add a quorum disk.
On the primary storage system, create the pairs.
```
paircreate -g oraHA -f never -vl -jq 0 -d dev1 -IH0
```
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.

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.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 (I/O might resume automatically).

Note: When the external storage system is installed at the primary site, if a failure occurs in both the primary storage system and the external storage system, forcibly delete the pair on the secondary storage system, and then re-create the pair. For details, see Recovering the storage systems: primary site failure with external storage system.

Confirming the CVS attribute on the external storage system

Interface	To confirm the CVS attribute:
CCI	Execute the `raidcom get ldev` command from CCI to the LDEV which is used as quorum disk by external storage system, and then confirm whether the CVS attribute is output for `VOL_TYPE`. Details of the `raidcom get ldev` command; refer to Command Control Interface Command Reference.
Web Console*	Confirm whether the CVS attribute is displayed in the CVS column on the LUN Management window.
* Ask the maintenance personnel to operate the Web Console.

Conditions for the CVS attribute for volumes created in the external storage system

Interface	Condition			CVS attribute
CCI	Internal volume or external volume			Allowed
	DP-VOL	VSP 5000 series, VSP G1x00, VSP F1500		Allowed
		VSP or earlier	Create LDEV of maximum size	Not allowed
		VSP or earlier	Create LDEV less than maximum size	Allowed
Web Console*	The LDEV is created during the operation of Define Config & Install or the installation of ECC/LDEV, with the initial value of the Number of LDEVs on the Device Emulation Type Define window.			Not allowed
Web Console*	Other than above			Allowed
* Ask the maintenance personnel to use the Web Console.