VxVM vxdiskunsetup ERROR V-5-2-2397 Veritas Disk Name: Device address must be of the form _
When I’m removing a disk from Veritas Volume Manager I was presented the following error message
root@solaris:/ # vxdg -g documentumdg rmdisk documentum01
root@solaris:/ # vxdiskunsetup -C documentum01
VxVM vxdiskunsetup ERROR V-5-2-2397 documentum01: Device address must be of the form _ where
is the logical name of the enclosure to which the
disk belongs
is the logical number of the disk
I need to specify the enclosure name and disk number so that it ran without errors
root@solaris:/ # vxdisk -o alldgs -e list | grep documentum01
dm documentum01 ibm_ds8x000_3134 – 62816000 – – – –root@solaris:/ # vxdiskunsetup -C ibm_ds8x000_3134
Rename disk group in Veritas Volume Manager
Listing the disk groups. I want to change usersdg to users175sbcdg
root@solaris:~ # vxdg list
NAME STATE ID
softwaredg enabled 1283277052.11.solaris
bkpcvrddg enabled,cds 1447967356.130.solaris
usersdg enabled,cds 1447967326.128.solaris
Deport the disk group
root@solaris:~ # vxdg deport usersdg
root@solaris:~ # vxdg list
NAME STATE ID
softwaredg enabled 1283277052.11.solaris
bkpcvrddg enabled,cds 1447967356.130.solaris
To rename the disk group, import the disk group using vxdg with the syntax shown below
root@solaris:~ # vxdg -n users175sbcdg import usersdg
root@solaris:~ # vxdg list
NAME STATE ID
softwaredg enabled 1283277052.11.solaris
bkpcvrddg enabled,cds 1447967356.130.solaris
users175sbcdg enabled,cds 1447967326.128.solaris
Renaming a disk in Veritas Volume Manager
Listing disks
root@solaris:~ # vxdisk -o alldgs -e list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
disk_43 auto:SVM – – SVM c1t10d0s2 –
disk_44 auto:sliced softmirr softwaredg online c1t11d0s2 –
disk_45 auto:sliced softdisk softwaredg online c0t9d0s2 –
disk_46 auto:SVM – – SVM c0t8d0s2 –
ibm_ds8x000_5169 auto:cdsdisk usersdgd01 users175sbcdg online c8t6005076308FFC2A70000000000005169d0s2 std
ibm_ds8x000_5170 auto:cdsdisk bkpcvrddgd01 bkpcvrd175sbcdg online c8t6005076308FFC2A70000000000005170d0s2 std
ibm_ds8x000_5171 auto – – nolabel c8t6005076308FFC2A70000000000005171d0s2 std
ibm_ds8x000_5172 auto – – nolabel c8t6005076308FFC2A70000000000005172d0s2 std
ibm_ds8x000_5173 auto – – nolabel c8t6005076308FFC2A70000000000005173d0s2 std
ibm_ds8x000_5174 auto – – nolabel c8t6005076308FFC2A70000000000005174d0s2 std
Renaming disk in disk group users175sbcdg named usersdgd01 to users175sbcd01
Renaming disk in disk group bkpcvrd175sbcdg named bkpcvrddgd01 to bkpcvrd175sbcd01
root@solaris:~ # vxedit -g users175sbcdg rename usersdgd01 users175sbcd01
root@solaris:~ # vxedit -g bkpcvrd175sbcdg rename bkpcvrddgd01 bkpcvrd175sbcd01
Listing disks
root@solaris:~ # vxdisk -o alldgs -e list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
disk_43 auto:SVM – – SVM c1t10d0s2 –
disk_44 auto:sliced softmirr softwaredg online c1t11d0s2 –
disk_45 auto:sliced softdisk softwaredg online c0t9d0s2 –
disk_46 auto:SVM – – SVM c0t8d0s2 –
ibm_ds8x000_5169 auto:cdsdisk users175sbcd01 users175sbcdg online c8t6005076308FFC2A70000000000005169d0s2 std
ibm_ds8x000_5170 auto:cdsdisk bkpcvrd175sbcd01 bkpcvrd175sbcdg online c8t6005076308FFC2A70000000000005170d0s2 std
ibm_ds8x000_5171 auto – – nolabel c8t6005076308FFC2A70000000000005171d0s2 std
ibm_ds8x000_5172 auto – – nolabel c8t6005076308FFC2A70000000000005172d0s2 std
ibm_ds8x000_5173 auto – – nolabel c8t6005076308FFC2A70000000000005173d0s2 std
ibm_ds8x000_5174 auto – – nolabel c8t6005076308FFC2A70000000000005174d0s2 std
Resizing a VXFS filesystem on Solaris
I will resize a filesystem with 4 LUNs with 500GB
First, checking disk group, volume and mount point
root@solaris:/ # df -h /usr/software/documentum/engineering
Filesystem size used avail capacity Mounted on
/dev/vx/dsk/documentumdg/ged_engineeringvol
9.3T 8.8T 473G 96% /usr/software/documentum/engineering
Storage team provided these four LUN IDs
6029 / 6030 / 6031 / 6032
Verifying which HBA card is online – c3 and c5
root@solaris:/ # fcinfo hba-port | egrep ‘OS Device Name|State’
OS Device Name: /dev/cfg/c11
State: offline
OS Device Name: /dev/cfg/c12
State: offline
OS Device Name: /dev/cfg/c9
State: offline
OS Device Name: /dev/cfg/c10
State: offline
OS Device Name: /dev/cfg/c4
State: offline
OS Device Name: /dev/cfg/c5
State: online
OS Device Name: /dev/cfg/c2
State: offline
OS Device Name: /dev/cfg/c3
State: online
Making the LUNs available to Solaris and Veritas Volume Manager
root@solaris:/ # cfgadm -c configure c5
root@solaris:/ # cfgadm -c configure c3
root@solaris:/ # devfsadm -C
root@solaris:/ # vxdctl enable
Searching for all 4 LUNs in Solaris
root@solaris:/ # echo | format | grep 6029
c6t6005076308FFC2A70000000000006029d0: configured with capacity of 499.98GB
4. c6t6005076308FFC2A70000000000006029d0
/scsi_vhci/ssd@g6005076308ffc2a70000000000006029root@solaris:/ # echo | format | grep 6030
c6t6005076308FFC2A70000000000006030d0: configured with capacity of 499.98GB
9. c6t6005076308FFC2A70000000000006030d0
/scsi_vhci/ssd@g6005076308ffc2a70000000000006030root@solaris:/ # echo | format | grep 6031
c6t6005076308FFC2A70000000000006031d0: configured with capacity of 499.98GB
11. c6t6005076308FFC2A70000000000006031d0
/scsi_vhci/ssd@g6005076308ffc2a70000000000006031root@solaris:/ # echo | format | grep 6032
c6t6005076308FFC2A70000000000006032d0: configured with capacity of 499.98GB
10. c6t6005076308FFC2A70000000000006032d0
/scsi_vhci/ssd@g6005076308ffc2a70000000000006032
Searching for all 4 LUNs in Veritas Volume Manager
root@solaris:/ # vxdisk -o alldgs -e list | egrep ‘6029|6030|6031|6032’
ibm_ds8x000_6029 auto – – nolabel c6t6005076308FFC2A70000000000006029d0s2 std
ibm_ds8x000_6030 auto – – nolabel c6t6005076308FFC2A70000000000006030d0s2 std
ibm_ds8x000_6031 auto – – nolabel c6t6005076308FFC2A70000000000006031d0s2 std
ibm_ds8x000_6032 auto – – nolabel c6t6005076308FFC2A70000000000006032d0s2 std
Apply label on all 4 disks
root@solaris:/ # format c6t6005076308FFC2A70000000000006029d0s2
c6t6005076308FFC2A70000000000006029d0s2: configured with capacity of 499.98GB
selecting c6t6005076308FFC2A70000000000006029d0s2
[disk formatted]FORMAT MENU:
disk – select a disk
type – select (define) a disk type
partition – select (define) a partition table
current – describe the current disk
format – format and analyze the disk
repair – repair a defective sector
label – write label to the disk
analyze – surface analysis
defect – defect list management
backup – search for backup labels
verify – read and display labels
save – save new disk/partition definitions
inquiry – show vendor, product and revision
volname – set 8-character volume name
! – execute , then return
quit
format> label
Ready to label disk, continue? yformat> q
The disks will show the status online invalid instead of nolabel
root@solaris:/ # vxdisk -o alldgs -e list | egrep ‘6029|6030|6031|6032’
ibm_ds8x000_6029 auto:none – – online invalid c6t6005076308FFC2A70000000000006029d0s2 std
ibm_ds8x000_6030 auto:none – – online invalid c6t6005076308FFC2A70000000000006030d0s2 std
ibm_ds8x000_6031 auto:none – – online invalid c6t6005076308FFC2A70000000000006031d0s2 std
ibm_ds8x000_6032 auto:none – – online invalid c6t6005076308FFC2A70000000000006032d0s2 std
I’ll be adding the LUNs to documentumdg. I follow a numerical order so I’m verifying which will be the next ones
root@solaris:/ # vxdisk -o alldgs -e list | grep documentumdg | sort -k3
ibm_ds8x000_3134 auto:cdsdisk documentum01 documentumdg online c6t6005076308FFC2A70000000000003134d0s2 std
ibm_ds8x000_6006 auto:cdsdisk documentum02 documentumdg online c6t6005076308FFC2A70000000000006006d0s2 std
ibm_ds8x000_3136 auto:cdsdisk documentum03 documentumdg online c6t6005076308FFC2A70000000000003136d0s2 std
ibm_ds8x000_6005 auto:cdsdisk documentum04 documentumdg online c6t6005076308FFC2A70000000000006005d0s2 std
ibm_ds8x000_3133 auto:cdsdisk documentum05 documentumdg online c6t6005076308FFC2A70000000000003133d0s2 std
ibm_ds8x000_6011 auto:cdsdisk documentum06 documentumdg online c6t6005076308FFC2A70000000000006011d0s2 std
ibm_ds8x000_6012 auto:cdsdisk documentum07 documentumdg online c6t6005076308FFC2A70000000000006012d0s2 std
ibm_ds8x000_6007 auto:cdsdisk documentum08 documentumdg online c6t6005076308FFC2A70000000000006007d0s2 std
ibm_ds8x000_6008 auto:cdsdisk documentum09 documentumdg online c6t6005076308FFC2A70000000000006008d0s2 std
ibm_ds8x000_6009 auto:cdsdisk documentum10 documentumdg online c6t6005076308FFC2A70000000000006009d0s2 std
ibm_ds8x000_6010 auto:cdsdisk documentum11 documentumdg online c6t6005076308FFC2A70000000000006010d0s2 std
ibm_ds8x000_6013 auto:cdsdisk documentum12 documentumdg online c6t6005076308FFC2A70000000000006013d0s2 std
ibm_ds8x000_6014 auto:cdsdisk documentum13 documentumdg online c6t6005076308FFC2A70000000000006014d0s2 std
ibm_ds8x000_6015 auto:cdsdisk documentum14 documentumdg online c6t6005076308FFC2A70000000000006015d0s2 std
ibm_ds8x000_6016 auto:cdsdisk documentum15 documentumdg online c6t6005076308FFC2A70000000000006016d0s2 std
ibm_ds8x000_6017 auto:cdsdisk documentum16 documentumdg online c6t6005076308FFC2A70000000000006017d0s2 std
ibm_ds8x000_6018 auto:cdsdisk documentum17 documentumdg online c6t6005076308FFC2A70000000000006018d0s2 std
ibm_ds8x000_6019 auto:cdsdisk documentum18 documentumdg online c6t6005076308FFC2A70000000000006019d0s2 std
ibm_ds8x000_6020 auto:cdsdisk documentum19 documentumdg online c6t6005076308FFC2A70000000000006020d0s2 std
ibm_ds8x000_6021 auto:cdsdisk documentum20 documentumdg online c6t6005076308FFC2A70000000000006021d0s2 std
ibm_ds8x000_6022 auto:cdsdisk documentum21 documentumdg online c6t6005076308FFC2A70000000000006022d0s2 std
ibm_ds8x000_6002 auto:cdsdisk documentum22 documentumdg online c6t6005076308FFC2A70000000000006002d0s2 std
ibm_ds8x000_6004 auto:cdsdisk documentum23 documentumdg online c6t6005076308FFC2A70000000000006004d0s2 std
ibm_ds8x000_6023 auto:cdsdisk documentum24 documentumdg online c6t6005076308FFC2A70000000000006023d0s2 std
ibm_ds8x000_6024 auto:cdsdisk documentum25 documentumdg online c6t6005076308FFC2A70000000000006024d0s2 std
ibm_ds8x000_6000 auto:cdsdisk documentum26 documentumdg online c6t6005076308FFC2A70000000000006000d0s2 std
ibm_ds8x000_6001 auto:cdsdisk documentum27 documentumdg online c6t6005076308FFC2A70000000000006001d0s2 std
ibm_ds8x000_6003 auto:cdsdisk documentum28 documentumdg online c6t6005076308FFC2A70000000000006003d0s2 std
ibm_ds8x000_6027 auto:cdsdisk documentum29 documentumdg online c6t6005076308FFC2A70000000000006027d0s2 std
ibm_ds8x000_6028 auto:cdsdisk documentum30 documentumdg online c6t6005076308FFC2A70000000000006028d0s2 std
All the disks in the disk group are formatted as cdsdisk. Configuring the disks to be used by Veritas Volume Manager
root@solaris:/ # vxdisksetup -i ibm_ds8x000_6029
root@solaris:/ # vxdisksetup -i ibm_ds8x000_6030
root@solaris:/ # vxdisksetup -i ibm_ds8x000_6031
root@solaris:/ # vxdisksetup -i ibm_ds8x000_6032
Checking the disks
root@solaris:/ # vxdisk -o alldgs -e list | egrep ‘6029|6030|6031|6032’
ibm_ds8x000_6029 auto:cdsdisk – – online c6t6005076308FFC2A70000000000006029d0s2 std
ibm_ds8x000_6030 auto:cdsdisk – – online c6t6005076308FFC2A70000000000006030d0s2 std
ibm_ds8x000_6031 auto:cdsdisk – – online c6t6005076308FFC2A70000000000006031d0s2 std
ibm_ds8x000_6032 auto:cdsdisk – – online c6t6005076308FFC2A70000000000006032d0s2 std
Adding them to documentumdg disk group
root@solaris:/ # vxdg -g documentumdg adddisk documentum31=ibm_ds8x000_6029
root@solaris:/ # vxdg -g documentumdg adddisk documentum32=ibm_ds8x000_6030
root@solaris:/ # vxdg -g documentumdg adddisk documentum33=ibm_ds8x000_6031
root@solaris:/ # vxdg -g documentumdg adddisk documentum34=ibm_ds8x000_6032
root@solaris:/ # vxdisk -o alldgs -e list | grep documentumdg | sort -k3
ibm_ds8x000_3134 auto:cdsdisk documentum01 documentumdg online c6t6005076308FFC2A70000000000003134d0s2 std
ibm_ds8x000_6006 auto:cdsdisk documentum02 documentumdg online c6t6005076308FFC2A70000000000006006d0s2 std
ibm_ds8x000_3136 auto:cdsdisk documentum03 documentumdg online c6t6005076308FFC2A70000000000003136d0s2 std
ibm_ds8x000_6005 auto:cdsdisk documentum04 documentumdg online c6t6005076308FFC2A70000000000006005d0s2 std
ibm_ds8x000_3133 auto:cdsdisk documentum05 documentumdg online c6t6005076308FFC2A70000000000003133d0s2 std
ibm_ds8x000_6011 auto:cdsdisk documentum06 documentumdg online c6t6005076308FFC2A70000000000006011d0s2 std
ibm_ds8x000_6012 auto:cdsdisk documentum07 documentumdg online c6t6005076308FFC2A70000000000006012d0s2 std
ibm_ds8x000_6007 auto:cdsdisk documentum08 documentumdg online c6t6005076308FFC2A70000000000006007d0s2 std
ibm_ds8x000_6008 auto:cdsdisk documentum09 documentumdg online c6t6005076308FFC2A70000000000006008d0s2 std
ibm_ds8x000_6009 auto:cdsdisk documentum10 documentumdg online c6t6005076308FFC2A70000000000006009d0s2 std
ibm_ds8x000_6010 auto:cdsdisk documentum11 documentumdg online c6t6005076308FFC2A70000000000006010d0s2 std
ibm_ds8x000_6013 auto:cdsdisk documentum12 documentumdg online c6t6005076308FFC2A70000000000006013d0s2 std
ibm_ds8x000_6014 auto:cdsdisk documentum13 documentumdg online c6t6005076308FFC2A70000000000006014d0s2 std
ibm_ds8x000_6015 auto:cdsdisk documentum14 documentumdg online c6t6005076308FFC2A70000000000006015d0s2 std
ibm_ds8x000_6016 auto:cdsdisk documentum15 documentumdg online c6t6005076308FFC2A70000000000006016d0s2 std
ibm_ds8x000_6017 auto:cdsdisk documentum16 documentumdg online c6t6005076308FFC2A70000000000006017d0s2 std
ibm_ds8x000_6018 auto:cdsdisk documentum17 documentumdg online c6t6005076308FFC2A70000000000006018d0s2 std
ibm_ds8x000_6019 auto:cdsdisk documentum18 documentumdg online c6t6005076308FFC2A70000000000006019d0s2 std
ibm_ds8x000_6020 auto:cdsdisk documentum19 documentumdg online c6t6005076308FFC2A70000000000006020d0s2 std
ibm_ds8x000_6021 auto:cdsdisk documentum20 documentumdg online c6t6005076308FFC2A70000000000006021d0s2 std
ibm_ds8x000_6022 auto:cdsdisk documentum21 documentumdg online c6t6005076308FFC2A70000000000006022d0s2 std
ibm_ds8x000_6002 auto:cdsdisk documentum22 documentumdg online c6t6005076308FFC2A70000000000006002d0s2 std
ibm_ds8x000_6004 auto:cdsdisk documentum23 documentumdg online c6t6005076308FFC2A70000000000006004d0s2 std
ibm_ds8x000_6023 auto:cdsdisk documentum24 documentumdg online c6t6005076308FFC2A70000000000006023d0s2 std
ibm_ds8x000_6024 auto:cdsdisk documentum25 documentumdg online c6t6005076308FFC2A70000000000006024d0s2 std
ibm_ds8x000_6000 auto:cdsdisk documentum26 documentumdg online c6t6005076308FFC2A70000000000006000d0s2 std
ibm_ds8x000_6001 auto:cdsdisk documentum27 documentumdg online c6t6005076308FFC2A70000000000006001d0s2 std
ibm_ds8x000_6003 auto:cdsdisk documentum28 documentumdg online c6t6005076308FFC2A70000000000006003d0s2 std
ibm_ds8x000_6027 auto:cdsdisk documentum29 documentumdg online c6t6005076308FFC2A70000000000006027d0s2 std
ibm_ds8x000_6028 auto:cdsdisk documentum30 documentumdg online c6t6005076308FFC2A70000000000006028d0s2 std
ibm_ds8x000_6029 auto:cdsdisk documentum31 documentumdg online c6t6005076308FFC2A70000000000006029d0s2 std
ibm_ds8x000_6030 auto:cdsdisk documentum32 documentumdg online c6t6005076308FFC2A70000000000006030d0s2 std
ibm_ds8x000_6031 auto:cdsdisk documentum33 documentumdg online c6t6005076308FFC2A70000000000006031d0s2 std
ibm_ds8x000_6032 auto:cdsdisk documentum34 documentumdg online c6t6005076308FFC2A70000000000006032d0s2 std
Checking available disk group space
root@solaris:/ # vxassist -g documentumdg maxsize
Maximum volume size: 4193908736 (2047807Mb)
Resizing volume and filesystem space
root@solaris:/ # vxresize -g documentumdg ged_engenhariavol +2047807M
root@solaris:/ # df -h /usr/software/documentum/fs_ged_engenharia_01
Filesystem size used avail capacity Mounted on
/dev/vx/dsk/documentumdg/ged_engineeringvol
11T 8.8T 2.4T 79% /usr/software/documentum/engineering
VxVM vxplex ERROR V-5-1-10870 fsgen/vxplex: Warning: vxsync exited with exitcode 42
Migrating data to a new storage. Instead of using vxevac we mirrored the volumes
After receiving confirmation that everything is ok, we started removing one side of the mirror.
root@solaris:/ # vxplex -g bkpdg det dat.bkpdg-01
VxVM vxsync INFO V-5-1-4514 VX_FREEZE_ALL ioctl failed
VxVM vxplex ERROR V-5-1-10870 fsgen/vxplex: Warning: vxsync exited with exitcode 42:
Volume data may not be flushed to all plexes
Checking the disk group
root@solaris:/ # vxprint -htg bkpdg
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATEdg bkpdg default default 3000 1222439090.134.prd007-sbc
dm bkpdgnew01 san_vc0_13 auto 16127 104792064 –
dm bkpdgnew02 san_vc0_28 auto 3839 16766976 –
dm bkpdgnew03 san_vc0_25 auto 16127 1048510464 –
dm bkpdgnew04 san_vc0_27 auto 3839 16766976 –
dm bkpdgnew05 san_vc0_14 auto 16127 104792064 –
dm bkpdgnew06 san_vc0_8 auto 3839 62904320 –
dm bkpdgnew07 san_vc0_21 auto 16127 146735104 –
dm bkpdgnew08 san_vc0_7 auto 16127 104792064 –
dm bkpdgnew09 san_vc0_24 auto 16127 209649664 –
dm bkpdgnew10 san_vc0_4 auto 16127 104792064 –
dm bkpdgnew11 san_vc0_6 auto 16127 104792064 –
dm bkpdg01 ibm_ds8x000_1153 auto 81663 106823680 –
dm bkpdg02 ibm_ds8x000_1167 auto 66943 18800640 –
dm bkpdg03 ibm_ds8x000_1164 auto 81663 1050542080 –
dm bkpdg04 ibm_ds8x000_1166 auto 66943 18800640 –
dm bkpdg05 ibm_ds8x000_1154 auto 81663 106823680 –
dm bkpdg06 ibm_ds8x000_1148 auto 81663 64880640 –
dm bkpdg07 ibm_ds8x000_1160 auto 81663 148766720 –
dm bkpdg08 ibm_ds8x000_1147 auto 81663 106823680 –
dm bkpdg09 ibm_ds8x000_1163 auto 81663 211681280 –
dm bkpdg10 ibm_ds8x000_1144 auto 81663 106823680 –
dm bkpdg11 ibm_ds8x000_1146 auto 81663 106823680 –v dat.bkpdg – ENABLED ACTIVE 2025293824 SELECT – fsgen
pl dat.bkpdg-01 dat.bkpdg DETACHED STALE 2025293824 CONCAT – RW
sd bkpdgnew01-01 dat.bkpdg-01 bkpdgnew01 0 104792064 0 san_vc0_13 ENA
sd bkpdgnew02-01 dat.bkpdg-01 bkpdgnew02 0 16766976 104792064 san_vc0_28 ENA
sd bkpdgnew03-01 dat.bkpdg-01 bkpdgnew03 0 1048510464 121559040 san_vc0_25 ENA
sd bkpdgnew04-01 dat.bkpdg-01 bkpdgnew04 0 16766976 1170069504 san_vc0_27 ENA
sd bkpdgnew05-01 dat.bkpdg-01 bkpdgnew05 0 104792064 1186836480 san_vc0_14 ENA
sd bkpdgnew06-01 dat.bkpdg-01 bkpdgnew06 0 62904320 1291628544 san_vc0_8 ENA
sd bkpdgnew07-01 dat.bkpdg-01 bkpdgnew07 0 146735104 1354532864 san_vc0_21 ENA
sd bkpdgnew08-01 dat.bkpdg-01 bkpdgnew08 0 104792064 1501267968 san_vc0_7 ENA
sd bkpdgnew09-01 dat.bkpdg-01 bkpdgnew09 0 209649664 1606060032 san_vc0_24 ENA
sd bkpdgnew10-01 dat.bkpdg-01 bkpdgnew10 0 104792064 1815709696 san_vc0_4 ENA
sd bkpdgnew11-01 dat.bkpdg-01 bkpdgnew11 0 104792064 1920501760 san_vc0_6 ENA
pl dat.bkpdg-02 dat.bkpdg ENABLED ACTIVE 2025293824 CONCAT – RW
sd bkpdg10-01 dat.bkpdg-02 bkpdg10 0 106823680 0 ibm_ds8x000_1144 ENA
sd bkpdg11-01 dat.bkpdg-02 bkpdg11 0 106823680 106823680 ibm_ds8x000_1146 ENA
sd bkpdg08-01 dat.bkpdg-02 bkpdg08 0 106823680 213647360 ibm_ds8x000_1147 ENA
sd bkpdg06-01 dat.bkpdg-02 bkpdg06 0 64880640 320471040 ibm_ds8x000_1148 ENA
sd bkpdg01-01 dat.bkpdg-02 bkpdg01 0 106823680 385351680 ibm_ds8x000_1153 ENA
sd bkpdg05-01 dat.bkpdg-02 bkpdg05 0 106823680 492175360 ibm_ds8x000_1154 ENA
sd bkpdg07-01 dat.bkpdg-02 bkpdg07 0 148766720 598999040 ibm_ds8x000_1160 ENA
sd bkpdg09-01 dat.bkpdg-02 bkpdg09 0 211681280 747765760 ibm_ds8x000_1163 ENA
sd bkpdg03-01 dat.bkpdg-02 bkpdg03 0 1050542080 959447040 ibm_ds8x000_1164 ENA
sd bkpdg04-01 dat.bkpdg-02 bkpdg04 0 15304704 2009989120 ibm_ds8x000_1166 ENA
We ignored the message and removed the plex. In the support page for Veritas it asks to stop the volume and after it shows that the volume is clean, you disassociate the plex. Check Veritas support page if you want to follow their instructions
root@solaris:/ # vxplex -g bkpdg -o rm dis dat.bkpdg-01
root@solaris:/ # vxprint -htg bkpdg
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATEdg bkpdg default default 3000 1222439090.134.prd007-sbc
dm bkpdgnew01 san_vc0_13 auto 16127 104792064 –
dm bkpdgnew02 san_vc0_28 auto 3839 16766976 –
dm bkpdgnew03 san_vc0_25 auto 16127 1048510464 –
dm bkpdgnew04 san_vc0_27 auto 3839 16766976 –
dm bkpdgnew05 san_vc0_14 auto 16127 104792064 –
dm bkpdgnew06 san_vc0_8 auto 3839 62904320 –
dm bkpdgnew07 san_vc0_21 auto 16127 146735104 –
dm bkpdgnew08 san_vc0_7 auto 16127 104792064 –
dm bkpdgnew09 san_vc0_24 auto 16127 209649664 –
dm bkpdgnew10 san_vc0_4 auto 16127 104792064 –
dm bkpdgnew11 san_vc0_6 auto 16127 104792064 –
dm bkpdg01 ibm_ds8x000_1153 auto 81663 106823680 –
dm bkpdg02 ibm_ds8x000_1167 auto 66943 18800640 –
dm bkpdg03 ibm_ds8x000_1164 auto 81663 1050542080 –
dm bkpdg04 ibm_ds8x000_1166 auto 66943 18800640 –
dm bkpdg05 ibm_ds8x000_1154 auto 81663 106823680 –
dm bkpdg06 ibm_ds8x000_1148 auto 81663 64880640 –
dm bkpdg07 ibm_ds8x000_1160 auto 81663 148766720 –
dm bkpdg08 ibm_ds8x000_1147 auto 81663 106823680 –
dm bkpdg09 ibm_ds8x000_1163 auto 81663 211681280 –
dm bkpdg10 ibm_ds8x000_1144 auto 81663 106823680 –
dm bkpdg11 ibm_ds8x000_1146 auto 81663 106823680 –v dat.bkpdg – ENABLED ACTIVE 2025293824 SELECT – fsgen
pl dat.bkpdg-02 dat.bkpdg ENABLED ACTIVE 2025293824 CONCAT – RW
sd bkpdg10-01 dat.bkpdg-02 bkpdg10 0 106823680 0 ibm_ds8x000_1144 ENA
sd bkpdg11-01 dat.bkpdg-02 bkpdg11 0 106823680 106823680 ibm_ds8x000_1146 ENA
sd bkpdg08-01 dat.bkpdg-02 bkpdg08 0 106823680 213647360 ibm_ds8x000_1147 ENA
sd bkpdg06-01 dat.bkpdg-02 bkpdg06 0 64880640 320471040 ibm_ds8x000_1148 ENA
sd bkpdg01-01 dat.bkpdg-02 bkpdg01 0 106823680 385351680 ibm_ds8x000_1153 ENA
sd bkpdg05-01 dat.bkpdg-02 bkpdg05 0 106823680 492175360 ibm_ds8x000_1154 ENA
sd bkpdg07-01 dat.bkpdg-02 bkpdg07 0 148766720 598999040 ibm_ds8x000_1160 ENA
sd bkpdg09-01 dat.bkpdg-02 bkpdg09 0 211681280 747765760 ibm_ds8x000_1163 ENA
sd bkpdg03-01 dat.bkpdg-02 bkpdg03 0 1050542080 959447040 ibm_ds8x000_1164 ENA
sd bkpdg04-01 dat.bkpdg-02 bkpdg04 0 15304704 2009989120 ibm_ds8x000_1166 ENA
Trying to install Storage Foundation Basic on CentOS? It doesn’t work
Running Storage Foundation Basic installer was giving me an error message saying perl was not found
root@centos6veritas:/tmp/veritas/dvd3-sfbasic/rhel6_x86_64# ./installer
Error: Cannot find perl to execute ./installer
The installer script checks the binary on the directory of your distribution/perl. Since this is not a genuine Red Hat Enterprise Linux, a workaround is needed.
root@centos6veritas:/tmp/veritas/dvd3-sfbasic/rhel6_x86_64/perl # ln -s RHEL6x8664 SLES10x8664
root@centos6veritas:/tmp/veritas/dvd3-sfbasic/rhel6_x86_64/perl # ls -l
total 4
drwxrwxr-x. 4 root root 4096 Oct 28 07:16 RHEL6x8664
lrwxrwxrwx. 1 root root 10 Feb 21 00:41 SLES10x8664 -> RHEL6x8664
Thanks to the Symantec Storage Foundation 6.2 Release Notes – Linux: Storage Foundation Basic cannot be installed on the Oracle Enterprise Linux platform (3651391) I found why the installer wasn’t working.
But in the end the installer will refuse to install and quit because it expects a Red Hat Enterprise Linux or Oracle Linux
Estimated time remaining: (mm:ss) 0:10 2 of 8
Checking system communication ………………………………………………………………………………………………………………………… Done
Checking release compatibility ……………………………………………………………………………………………………………………… FailedSystem verification checks completed
The following errors were discovered on the systems:
CPI ERROR V-9-20-1208 This release is intended to operate on OL and RHEL Linux distributions but centos6veritas is a CentOS system
installer log files and summary file are saved at:
/opt/VRTS/install/logs/installer-201502210042QRK
Would you like to view the summary file? [y,n,q] (n)
Reattach plex to the volume in Veritas Volume Manager
Some systems have the boot disk encapsulated in Veritas and it is mirrored
root@solaris:/ # vxprint -htg rootdg -v rootvol
V NAME RVG KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODEv rootvol – ENABLED ACTIVE 14338107 ROUND – root
pl rootvol-01 rootvol ENABLED ACTIVE 14338107 CONCAT – RW
sd rootdisk-B0 rootvol-01 rootdisk 71124290 1 0 c0t0d0 ENA
sd rootdisk-02 rootvol-01 rootdisk 0 14338106 1 c0t0d0 ENA
This volume should have at least two plexes, so there are plexes currently disabled on this disk group.
root@solaris:/ # vxprint -htg rootdg | grep DISABLED
pl local-02 – DISABLED – 6292242 CONCAT – RW
sd rootmirr-09 local-02 rootmirr 51897995 6292242 0 c0t1d0 ENApl rootvol-02 – DISABLED – 14338107 CONCAT – RW
sd rootmirr-01 rootvol-02 rootmirr 2888 14338107 0 c0t1d0 ENA
To attach this plex to the volume type the command below
root@solaris:/ # vxplex -g rootdg att rootvol rootvol-02
Veritas will not release the shell until it completes the task. Open another terminal and type vxtask list to check the status
root@solaris:/ # vxtask list
TASKID PTID TYPE/STATE PCT PROGRESS
180 ATCOPY/R 60.16% 0/14338107/8626432 PLXATT rootvol 0.0
After it is finished, check the volume again. It should have two plexes like in the example below
root@solaris:/ # vxprint -htg rootdg -v rootvol
V NAME RVG KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODEv rootvol – ENABLED ACTIVE 14338107 ROUND – root
pl rootvol-01 rootvol ENABLED ACTIVE 14338107 CONCAT – RW
sd rootdisk-B0 rootvol-01 rootdisk 71124290 1 0 c0t0d0 ENA
sd rootdisk-02 rootvol-01 rootdisk 0 14338106 1 c0t0d0 ENA
pl rootvol-02 rootvol ENABLED ACTIVE 14338107 CONCAT – RW
sd rootmirr-01 rootvol-02 rootmirr 2888 14338107 0 c0t1d0 ENA
How to discover the version of Veritas Explorer currently installed
To discover the version, simply run the tool with the -help flag.
root@solaris:/opt/VRTSspt/VRTSexplorer # ./VRTSexplorer -help
VRTSexplorer: version 4.0i
Usage: VRTSexplorer [ help | -help ] | [+v] [ module … ] | [+v] [ -module … ]
list of modules: vxvm vxfs fw vxld dbed edition.dro edition.sybed vcs visnS visnC spc txpt vsap vrtsisp isis gcm vmsa vras vfr ndmp samba spnas vnas glm dbac td web lic vlic vrw picd nbu cca cpi vxat vxaz ccs
Volume inside a Disk Group in Veritas Volume Manager is in NEEDSYNC state
Whenever you see a volume inside a disk group with the NEEDSYNC state, you simply run vxvol -g <disk group> resync <volume> to change the status back to ACTIVE.
root@solaris:/ # vxprint -htg softwaredg
DG NAME NCONFIG NLOG MINORS GROUP-ID
DT NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME NVOLUME KSTATE STATE
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCOdg softwaredg default default 38000 1185222274.13.solaris
dm softwaredg01 c0t9d0s2 auto 20095 286657920 –
dm softwaredg02 c1t11d0s2 auto 20095 286657920 –v app.software – ENABLED NEEDSYNC 14680064 SELECT – fsgen
pl app.software-01 app.software ENABLED ACTIVE 14680064 CONCAT – RW
sd softwaredg01-01 app.software-01 softwaredg01 0 14680064 0 c0t9d0 ENA
pl app.software-02 app.software ENABLED ACTIVE 14680064 CONCAT – RW
sd softwaredg02-01 app.software-02 softwaredg02 0 14680064 0 c1t11d0 ENAv ctm.oracatrman – ENABLED NEEDSYNC 2097152 SELECT – fsgen
pl ctm.oracatrman-01 ctm.oracatrman ENABLED ACTIVE 2097152 CONCAT – RW
sd softwaredg01-02 ctm.oracatrman-01 softwaredg01 14680064 2097152 0 c0t9d0 ENA
pl ctm.oracatrman-02 ctm.oracatrman ENABLED ACTIVE 2097152 CONCAT – RW
sd softwaredg02-04 ctm.oracatrman-02 softwaredg02 27262976 2097152 0 c1t11d0 ENAv dat.audit – ENABLED NEEDSYNC 4194304 SELECT – fsgen
pl dat.audit-01 dat.audit ENABLED ACTIVE 4194304 CONCAT – RW
sd softwaredg01-03 dat.audit-01 softwaredg01 16777216 4194304 0 c0t9d0 ENA
pl dat.audit-02 dat.audit ENABLED ACTIVE 4194304 CONCAT – RW
sd softwaredg02-03 dat.audit-02 softwaredg02 23068672 4194304 0 c1t11d0 ENAv dat.users – ENABLED NEEDSYNC 8388608 SELECT – fsgen
pl dat.users-01 dat.users ENABLED ACTIVE 8388608 CONCAT – RW
sd softwaredg01-04 dat.users-01 softwaredg01 20971520 8388608 0 c0t9d0 ENA
pl dat.users-02 dat.users ENABLED ACTIVE 8388608 CONCAT – RW
sd softwaredg02-02 dat.users-02 softwaredg02 14680064 8388608 0 c1t11d0 ENAv vol01 – ENABLED ACTIVE 10240000 SELECT – fsgen
pl vol01-01 vol01 ENABLED ACTIVE 10240000 CONCAT – RW
sd softwaredg01-05 vol01-01 softwaredg01 29360128 10240000 0 c0t9d0 ENA
pl vol01-02 vol01 ENABLED ACTIVE 10240000 CONCAT – RW
sd softwaredg02-05 vol01-02 softwaredg02 29360128 10240000 0 c1t11d0 ENA
root@solaris:/ # vxvol -g softwaredg resync dat.audit
Veritas Volume Manager – You don’t have permission to run
This is what happens when you try to run the vxdg command and doesn’t have permission.
username@hostname:/ $ vxdg list
vxvm:vxdg: ERROR: IPC failure: Permission denied
