Expanding the capacity of a DP-VOL used in a GAD pair

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

There are different procedures for expanding the capacity of a DP-VOL used as a volume in a GAD pair depending on whether the volume is also used by another software product such as Universal Replicator or Thin Image Advanced.

Use the following procedure to expand the DP-VOL capacity when the DP-VOL is not shared and is used only as a GAD pair volume.

Note:

Only the assigned page capacity out of the DP-VOL capacity is counted as the GAD license capacity.
Some operations (such as releasing pages) might change the page capacity of the P-VOL or S-VOL. If that occurs, the license capacity or the page capacity counted as the license capacity might differ between the P-VOL and S-VOL.

The V-VOL to be expanded must not be an external volume.
LDEV formatting must not be in process on the DP-VOL to be expanded.
The pool containing the DP-VOL to be expanded must meet the following conditions:
- The pool is in the Normal condition.
- The pool is not being shrunk.
Before expanding the volume capacity, make sure that there is enough GAD license capacity for the page capacity assigned to the expanded volume.

Verify that both the P-VOL and S-VOL of the GAD pair meet the prerequisites.
Display the detailed information about the GAD pair by using the CCI pairdisplay command.
Verify whether the current differential data management method is shared memory (SM) difference management or hierarchical difference management. The DM column displayed by the pairdisplay command shows whether shared memory (S) difference management or hierarchical (D) difference management is applied.
```
# pairdisplay -g oradb -fe
Group PairVol(L/R) (Port#,TID, LU),Seq#, LDEV#.P/S,Status,Fence,Seq#, P-LDEV# M CTG JID AP EM E-Seq# E-LDEV# R/W QM DM P
oradb dev1(L) (CL5-A-0,30, 0) 64568 301.P-VOL PAIR ASYNC,64568 303 - 0 2 1 - - - -/- AA S N
oradb dev1(R) (CL5-A-0,30, 2) 64568 303.S-VOL PAIR ASYNC,----- 301 - 0 4 1 - - - -/- AA S N
oradb dev2(L) (CL5-A-0,30, 1) 64568 302.P-VOL PAIR ASYNC,64568 304 - 0 3 1 - - - -/- AA D N
oradb dev2(R) (CL1-A-0,30, 3) 64568 304.S-VOL PAIR ASYNC,----- 302 - 0 5 1 - - - -/- AA D N
```
- If SM difference management is applied, go to step 3 to temporarily change to hierarchical difference management.
- If hierarchical difference management is applied, go to step 4.
Change the differential data management method to hierarchical difference management.
(For VSP One Block 85) Do so for both the P-VOL and the S-VOL. If the P-VOL and the S-VOL are on different types of storage systems, change the differential data management method on each storage system.
1. Change the system settings for hierarchical difference management.
  (For VSP One Block 85) Set advanced system settings No. 5 to ON and No. 6 to OFF by using the raidcom modify user_system_opt command.
  Command example:
```
raidcom modify user_system_opt -opt_id 5 -opt enable
```
```
raidcom modify user_system_opt -opt_id 6 -opt disable
```
  (For VSP One Block 20 series) Set system option modes (SOMs) 1198 to ON and 1199 to OFF by using the raidcom modify system_opt command.
  
  Command example:
```
raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode enable
```
```
raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode disable
```
2. Suspend the GAD pair.
3. Resynchronize the GAD pair.
4. Display the detailed information about the GAD pair by using the pairdisplay command.
  Verify that the current differential data management method is hierarchical difference management.
Suspend the GAD pair.
Expand the S-VOL capacity in the GAD pair.
Add the -request_id auto option to the raidcom extend ldev command to specify asynchronous command processing.
Command example

The following command expands the capacity of LDEV#44:44 by 10 GB.
```
raidcom extend ldev -ldev_id 0x4444 -capacity 10G –request_id auto -IH1
```
Note: A maximum of 65,280 request IDs can be assigned to one storage system. If there is no available request ID, the command fails with EX_IDEXHA. If that occurs, see the description of the function of request IDs in the Command Control Interface Command Reference and release request IDs.
Verify that expanding the S-VOL capacity in the GAD pair is finished.
Use the raidcom get command_status command to verify that the raidcom extend ldev command has finished processing.
Command example
```
raidcom get command_status -request_id <request#> -IH1
```
Replace <request#> with the request ID that was displayed in step 5.

Verify the expanded LDEV capacity using the raidcom get ldev command.
```
raidcom get ldev -ldev_id 0x4444 -fx -IH1
```
Confirm that asynchronous command processing has completed, and then release a request ID.
```
raidcom reset command_status -request_id <request#> -IH1
```
Expand the P-VOL capacity in the GAD pair in the same way as the S-VOL capacity.
If the P-VOL capacity in the GAD pair cannot be expanded, see Recovering from failure if one volume capacity in GAD pair cannot be expanded.
Verify that expanding the P-VOL capacity in the GAD pair is complete in the same way as the S-VOL capacity.
Resynchronize the GAD pair.
If the resync operation in the GAD pair cannot be performed, see Recovering from failure if one volume capacity in GAD pair cannot be expanded.
Verify that the pair statuses of both the P-VOL and S-VOL in the GAD pair have changed to PAIR (Mirror(RL)), and that the volume capacity is not being expanded.
If using CCI, check that the P column of the pairdisplay command displays N.
```
# pairdisplay -g oradb -fe
Group PairVol(L/R) (Port#,TID, LU),Seq#, LDEV#.P/S,Status,Fence,Seq#, P-LDEV# M CTG JID AP EM E-Seq# E-LDEV# R/W QM DM P
oradb dev1(L) (CL5-A-0,30, 0) 64568 301.P-VOL PAIR ASYNC,64568 303 - 0 2 1 - - - L/M AA S N
oradb dev1(R) (CL5-A-0,30, 2) 64568 303.S-VOL PAIR ASYNC,----- 301 - 0 4 1 - - - L/M AA S N
oradb dev2(L) (CL5-A-0,30, 1) 64568 302.P-VOL PAIR ASYNC,64568 304 - 0 3 1 - - - L/M AA D N
oradb dev2(R) (CL1-A-0,30, 3) 64568 304.S-VOL PAIR ASYNC,----- 302 - 0 5 1 - - - L/M AA D N
```
The P column in the pairdisplay command displays the status that the volume capacity is being expanded. An N indicates that the volume capacity is not being expanded, an E indicates that the volume capacity is being expanded.

The E status is displayed after expanding the P-VOL or S-VOL capacity in the GAD pair, and before performing the pair resync operation. This status changes to N after the resync operation completes.
If you temporarily changed the differential data management method from SM difference to hierarchical difference (Step 2), change back to SM difference management.
(For VSP One Block 85) Do so for both the P-VOL and the S-VOL. If the P-VOL and the S-VOL are on different types of storage systems, change the differential data management method on each storage system.
1. To change back to the SM difference management method:
  (For VSP One Block 85) Set advanced system settings No. 5 to ON and No. 6 to ON by using the raidcom modify user_system_opt command.
  Command example:
```
raidcom modify user_system_opt -opt_id 5 -opt enable
```
```
raidcom modify user_system_opt -opt_id 6 -opt enable
```
  (For VSP One Block 20 series) Set SOMs 1198 to OFF and 1199 to ON by using the raidcom modify system_opt command.
  Command example:
```
raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode disable
```
```
raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode enable
```
2. Suspend the GAD pair.
3. Resynchronize the GAD pair.
4. Display the detailed information about the GAD pair by using the pairdisplay command, and then verify that the current differential data management method is SM difference management.
5. (For VSP One Block 20 series) If the settings of SOMs 1198 and 1199 have been changed, set SOMs 1198 to OFF and 1199 to OFF by using the raidcom modify system_opt command.
  Command example:
```
raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode disable
```
```
raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode disable
```
  (For VSP One Block 85) If the settings of advanced system settings No. 5 and No. 6 have been changed, set advanced system settings No. 5 to OFF and No. 6 to OFF by using the raidcom modify user_system_opt command.
  Command example:
```
raidcom modify user_system_opt -opt_id 5 -opt disable
```
```
raidcom modify user_system_opt -opt_id 6 -opt disable
```