Problem
Cannot import a disk group due to it being at a lower disk group version 110/120.
Error Message
VxVM vxdg ERROR V-5-1-10978 Disk group datadg: import failed:
Disk group version doesn't support feature; see the vxdg upgrade command
Cause
Importing to a host that is running a different version of Storage Foundation, or (Business Critical Volume) BCV does not import to a host running a more recent version.
Solution
1. Below we see the disk group is at 120. We want it at 160 in order to import to the new host.
# vxdg list timdg
Group: timdg
dgid: 1371483032.57.mtvat1000-c9l.mvw.spt.Veritas.com
import-id: 1024.56
flags: cds
version: 120
|
2. Checking vxprint.
# vxprint -htg timdg
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 KSTATE
dg timdg default default 18000 1371483032.57.mtvat1000-c9l.mvw.spt.Veritas.com
dm timdg01 ams_wms0_144 auto 65536 1931008 -
dm timdg02 ams_wms0_145 auto 65536 1931008 -
v vol01 - ENABLED ACTIVE 2097152 SELECT - fsgen
pl vol01-01 vol01 ENABLED ACTIVE 2097152 CONCAT - RW
sd timdg01-01 vol01-01 timdg01 0 1931008 0 ams_wms0_144 ENA
sd timdg02-01 vol01-01 timdg02 0 166144 1931008 ams_wms0_145 ENA
|
3. Mount, and check the data on the source system.
# mount -f vxfs /dev/vx/dsk/timdg/vol01 /mnt
# df -k | grep vol01
/dev/vx/dsk/timdg/vol01 1048576 18542 965780 2% /mnt
# cd /mnt
# ls
TIMEZONE cfgadm device.tab fmthard gnome-vfs-mime-magic inetd.conf
aggregation.conf chroot devlink.tab format group init
aliases clri dgroup.tab format.dat grpck initpipe
amftab coreadm.conf driver_aliases fsck halt lost+found
auto_datastorm cron driver_classes fsdb hba.conf
auto_evidence dacf.conf dumpadm.conf fstyp hostname.bge0
auto_home datemsk dumpdates fuser hosts
auto_master dcopy esd.conf gabtab hosts-012312_133219
autopush defaultrouter ff getty ima.conf
|
4. Here we create the file that we will eventually use to rebuild the disk group objects.
# vxprint –g timdg –m > timdg.rebuild
# umount /mnt
# vxvol -g timdg stopall
# vxdg destroy timdg
# vxdg list
NAME STATE ID
datadg1 enabled,shared,cds 1349716524.20.mtvat1000-c9l.mvw.spt.Veritas.com
datadg2 enabled,shared,cds 1349716609.22.mtvat1000-c9l.mvw.spt.Veritas.com
timdg02 enabled,cds 1366315414.43.mtvat1000-c9l.mvw.spt.Veritas.com
# cat timdg.rebuild | vxprint -D - -mpvshr > timdg.rebuild2
|
5. Present the luns to the new host, and ftp over the file that was created with the above command. The luns should still be initialized under VxVM control, but have no disk group. We will recreate it with the below commands, but at disk group version 160.
# vxdg -T 160 init timdg timdg01=ams_wms0_144 timdg02=ams_wms0_145 |
6. Now we rebuild our objects (sub-disks, plex, and volumes).
# /usr/sbin/vxmake -g timdg -d timdg.rebuild2 |
7. Force start the volume as the volume/s may be reporting empty, or disabled.
# vxvol -g timdg -f start vol01 |
8. Now check for the new disk group version.
# vxdg list timdg
Group: timdg
dgid: 1371484638.63.mtvat1000-c9l.mvw.spt.Veritas.com
import-id: 1024.62
flags: cds
version: 160 <<<<< Now we are at version 160
# vxprint -htg timdg
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 KSTATE
dg timdg default default 10000 1371484638.63.mtvat1000-c9l.mvw.spt.Veritas.com
dm timdg01 ams_wms0_144 auto 65536 1931008 -
dm timdg02 ams_wms0_145 auto 65536 1931008 -
v vol01 - ENABLED ACTIVE 2097152 SELECT - fsgen
pl vol01-01 vol01 ENABLED ACTIVE 2097152 CONCAT - RW
sd timdg01-01 vol01-01 timdg01 0 1931008 0 ams_wms0_144 ENA
sd timdg02-01 vol01-01 timdg02 0 166144 1931008 ams_wms0_145 ENA
# mount -f vxfs /dev/vx/dsk/timdg/vol01 /mnt
# cd /mnt
# ls
TIMEZONE defaultrouter gabtab
aggregation.conf device.tab getty
aliases devlink.tab gnome-vfs-mime-magic
amftab dgroup.tab group
auto_datastorm driver_aliases grpck
auto_evidence driver_classes halt
auto_home dumpadm.conf hba.conf
auto_master dumpdates hostname.bge0
autopush esd.conf hosts
cfgadm ff hosts-012312_133219
chroot fmthard ima.conf
clri format inetd.conf
coreadm.conf format.dat init
cron fsck initpipe
dacf.conf fsdb lost+found
datemsk fstyp
dcopy fuser
|
9. All data is intact. The above procedure can also be used to simply back, and rebuild disk groups should need be during a service outage. Of course in this circumstance the disk will have to be reinitialized should the disk group configs get lost.
References
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.