Normal VG to Enhanced Concurrent VG

Hi All,

I am going to perform some activity in 2Node HA Server(Active/Passive).
For that i have to do some pre-requsite (ie., Resource Group VG's should be Enhanced-Concurrent)
In my setup, we have two volume groups in one RG. In that one VG is Normal and another is Enhance Concurrent.

How to convert Normal to Enhanced-Concurrent VG? by ONLINE without impact in production.

bash-3.2$ lspv
hdisk0          00f8e214bab2d2f3                    rootvg          active
hdisk1          00f8e214bab2d31b                    rootvg          active
hdisk2          00c6fd246d484e56                    datavg          active
hdisk4          00c6fe6473379021                    HBVG            concurrent
hdisk5          00c6fd2458a2ffe3                    siebelvg        active
hdisk6          00c6ff94bc5548ec                    siebelfsvg      concurrent
hdisk7          00c6ff94bc554cd6                    siebelfsvg      concurrent
bash-3.2$



bash-3.2$ lsvg siebelfsvg
VOLUME GROUP:       siebelfsvg               VG IDENTIFIER:  00c6ff9400004c0000000123bc5559f4
VG STATE:           active                   PP SIZE:        128 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      3198 (409344 megabytes)
MAX LVs:            256                      FREE PPs:       1517 (194176 megabytes)
LVs:                2                        USED PPs:       1681 (215168 megabytes)
OPEN LVs:           2                        QUORUM:         2 (Enabled)
TOTAL PVs:          2                        VG DESCRIPTORS: 3
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         2                        AUTO ON:        no
Concurrent:         Enhanced-Capable         Auto-Concurrent: Disabled
VG Mode:            Concurrent
Node ID:            3                        Active Nodes:
MAX PPs per VG:     32768                    MAX PVs:        1024
LTG size (Dynamic): 1024 kilobyte(s)         AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable
MIRROR POOL STRICT: off
PV RESTRICTION:     none                     INFINITE RETRY: no
 




bash-3.2$ lsvg siebelvg
VOLUME GROUP:       siebelvg                 VG IDENTIFIER:  00c6fd2400004c000000013c58a3002d
VG STATE:           active                   PP SIZE:        256 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      271 (69376 megabytes)
MAX LVs:            256                      FREE PPs:       150 (38400 megabytes)
LVs:                2                        USED PPs:       121 (30976 megabytes)
OPEN LVs:           2                        QUORUM:         2 (Enabled)
TOTAL PVs:          1                        VG DESCRIPTORS: 2
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         1                        AUTO ON:        no
MAX PPs per VG:     32512
MAX PPs per PV:     1016                     MAX PVs:        32
LTG size (Dynamic): 1024 kilobyte(s)         AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable
PV RESTRICTION:     none                     INFINITE RETRY: no
bash-3.2$




bash-3.2$
bash-3.2$ cllsres
APPLICATIONS="gateway"
CONCURRENT_VOLUME_GROUP="HBVG"
EXPORT_FILESYSTEM="/siebelfs_nfs"
FILESYSTEM=""
FORCED_VARYON="false"
FSCHECK_TOOL="fsck"
FS_BEFORE_IPADDR="true"
MOUNT_FILESYSTEM="/siebelfs;/siebelfs_nfs"
NFS_NETWORK="net_ether_01"
RECOVERY_METHOD="sequential"
SERVICE_LABEL="PRDSGW"
SSA_DISK_FENCING="false"
VG_AUTO_IMPORT="false"
VOLUME_GROUP="siebelvg siebelfsvg"
bash-3.2$
 
 

Thanks,
Thala

1st you need to make sure that "siebelvg" is going to be shared between nodes? if its not then you don't need to enable enhance concurrent on that, and if you are sharing the VG then
Change the VG to Big VG
run

lsvg siebelvg | egrep "MAX PVs:"   --> look for PV, for normal VG it will be 32

chvg -B siebelvg     --> This will change the VG to Big VG and this is dynamic, no need to varyoff vg.

lsvg siebelvg | egrep "MAX PVs:"   --> The PV no increases to 128

Now run 
lsattr -El siebelvg  --> ( and look for below)
auto_on       y 
....
conc_capable  n
....
Run

chvg -C siebelvg   --> This command will change the VG to enhance concurrent capable, and this is dynamic, no need to varyoff vg.

lsattr -El siebelvg  --> ( and look for below)
auto_on       n     --> Auto varyon will change to no
....
conc_capable  y   --> Enhance concurrent capable is changed to yes.
....
1 Like

What ibmtech told you is correct, just two things to add:

  1. When you make changes to the VGs on one node you need to do a "learning import" of the respective VG on the other node:
importvg -L <vgname> <hdisk>

This needs to be done to synchronize VG information across nodes. Otherwise the next takeover might just fail.

  1. For your VG to support ECC you need to have a storage underneath which supports concurrent access to the disks. Our old Clariion, for instance, did not.

I hope this helps.

bakunin

1 Like