Restore a Private Region on a disk.

NOTE these notes where taken after a call with Symantec please don't run this wi thout speaking to Symantec first. PROBLEM: You are getting the following error when importing a disk group, you ha ve just upgraded from VERITAS 4.1 5.1 # vxdg -C import kchdg VxVM vxdg ERROR V-5-1-587 Disk group kchdg: import failed: Disk group has no val id configuration A call was then opened with Symantec that requested the output of the following command which checks the configuration. # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS Disk_0 auto:SVM SVM Disk_1 auto:SVM SVM EMC3_06B7 auto:cdsdisk online EMC3_054D auto:cdsdisk online EMC4_0609 auto:cdsdisk online EMC4_0926 auto:cdsdisk online EMC5_2DEF auto:cdsdisk (kchquorumdg) online EMC5_2D70 auto:cdsdisk (kchdg) online EMC6_17A0 auto:cdsdisk (kchquorumdg) online EMC6_27C6 auto:cdsdisk (kchquorumdg) online Get the disk names of the problem diskgroup in this case it is EMC5_2D70 Get the underlying disks that are associated with this device. # vxdisk list EMC5_2D70| tail -2 c3t5006048C52A863DDd144s2 state=enabled c4t5006048C52A863D2d144s2 state=enabled Take the cXtXdX name and run the following command /etc/vx/diag.d/vxprivutil dumpconfig /dev/rdsk/c3t5006048C52A863DDd144s2 |vxprin t -D - -htThis will dump the config of the private region on the disk, from this you can see if there are duplicates where there shouldn't be, if there is then your private region is corrupt and needs recreated. First step to recreate and not have to reinitialise the disks etc is to try and use a previous backup of the disk group. These are taken every time the disk gro up is updates so fingers crossed you have one. # cd /etc/vx/cbr/bk/kchdg.1333032959.69.kchnode1 # ls -l -rw-r--r-- 1 root root 655360 Apr 3 17:36 config -rw-r--r-- 1 root root 655360 Apr 3 13:36 config.1 -rw-r--r-- 1 root root 15145 Apr 3 17:36 rec -rw-r--r-- 1 root root 15070 Apr 3 13:36 rec.1 -rw-r--r-- 1 root root 1804 Apr 3 17:36 nfo

1333032959.69.kchnode1.bin 1333032959.69.kchnode1.bin 1333032959.69.kchnode1.cfg 1333032959.69.kchnode1.cfg 1333032959.69.kchnode1.dgi

-rw-r--r-nfo.1 -rw-r--r-kinfo -rw-r--r-kinfo.1

1 root 1 root 1 root

root root root

1804 Apr 3 13:36 1333032959.69.kchnode1.dgi 2544 Apr 3 17:36 1333032959.69.kchnode1.dis 2544 Apr 3 13:36 1333032959.69.kchnode1.dis

Try and restore from a previous config # cat 1333032959.69.kchnode1.cfgrec |vxprint -D - -ht # /opt/VRTS/bin/vxconfigrestore -p kchdg Now the above command will either work or it won't, if it does then YAY if it do esn't then you will have to reinitialise the disks and volume group. But we are only touching the Private Region so all the data SHOULD be fine if we get our nu mbers correct. Reinitialise the disk Ok to reinitialise your private region you need a few imports bits of informatio n, here is a sample output of the disk i am going to reinitialise. # vxdisk list EMC5_2D70 | egrep -i '^public|^private' public: slice=2 offset=65792 len=4390528 disk_offset=0 private: slice=2 offset=256 len=65536 disk_offset=0 Ok here is the command to initialise the disk, and the information for the comma nd was found in the above output. # vxdisk -f init EMC5_2D70 privoffset=256 privlen=65536 puboffset=65792 publen=4 390528Hope that makes sense? Next you need to tell it what the subdisks are you can get this info from your p revious conifg # cat 1333032959.69.kchnode1.cfgrec |vxprint -D - -ht Disk group: kchdg DG ST DM RV RL CO VT V PL SD SV SC DC SP EX SR NAME NAME NAME NAME NAME NAME NAME NAME NAME NAME NAME NAME NAME NAME NAME NAME NCONFIG STATE DEVICE RLINK_CNT RVG CACHEVOL RVG RVG/VSET/CO VOLUME PLEX PLEX PLEX PARENTVOL SNAPVOL ASSOC KSTATE default EMC5_2D70 NLOG DM_CNT TYPE KSTATE KSTATE KSTATE KSTATE KSTATE KSTATE DISK VOLNAME CACHE LOGVOL DCO VC MINORS GROUP-ID SPARE_CNT PRIVLEN PUBLEN STATE PRIMARY STATE REM_HOST STATE STATE NVOLUME STATE LENGTH STATE LENGTH DISKOFFS LENGTH NVOLLAYR LENGTH DISKOFFS LENGTH APPVOL_CNT STATE DATAVOLS SRL REM_DG REM_RLNK READPOL LAYOUT [COL/]OFF [COL/]OFF [COL/]OFF PREFPLEX NCOL/WID DEVICE AM/NM DEVICE UTYPE MODE MODE MODE MODE

PERMS

MODE

STATE

dg kchdg dm kchdg01

default 32000 auto 2048

1141998863.35.acslsn 35688576 -

v pl sd pl sd

kchbackup ENABLED ACTIVE 14714880 SELECT fsgen kchbackup-01 kchbackup ENABLED ACTIVE 14714880 CONCAT RW kchdg01-01 kchbackup-01 kchdg01 20972576 14714880 0 EMC5_2D70 ENA acslsbackup-02 kchbackup ENABLED ACTIVE LOGONLY CONCAT RW kchdg01-02 kchbackup-02 kchdg01 20972048 528 LOG EMC5_2D70 ENA fsgen RW ENA RW ENA applied t

v kchhome ENABLED ACTIVE 20971520 SELECT pl kchhome-01 kchhome ENABLED ACTIVE 20971520 CONCAT sd kchdg01-01 kchhome-01 kchdg01 528 20971520 0 EMC5_2D70 pl kchhome-02 kchhome ENABLED ACTIVE LOGONLY CONCAT sd kchdg01-02 kchhome-02 kchdg01 0 528 LOG EMC5_2D70 Create a file that will make all your disk configuration, this is then o the diskgroup to set it up as before

# cat 1333032959.69.kchnode1.cfgrec |vxprint -D - -mvphsr > vxmake.out initialise the disk EMC5_2D70 to what the dm device was before which in this occ asion was kchdg01 # vxdg init kchdg kchdg01=EMC5_2D70Now update the diskgroup information with the vxmake.out file you created. This will restore it to it's former glory # vxmake -g kchdg -d vxmake.outStart the volumes # vxvol -g kchdg -f startallWhen you run a vxprint -htg kchdg you will notice th at not all the volumes will be online. # vxvol -g kchdg init active kchbackup # vxvol -g kchdg init active kchhomeNow all should look good when you run # vxprint -htg kchdg And continue to mount your filesystems :D you might have to perform a fsck on it first but all should be fine # mount /dev/vx/dsk/kchdg/kchhome /export/home