Rebuilding the DiskGroup in the event of import failure as the disk group is at a lower version
Article ID: 100009727
Updated On:
Description
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.
Resolution
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 timdgGroup: timdgdgid: 1371483032.57.mtvat1000-c9l.mvw.spt.Veritas.comimport-id: 1024.56flags: cdsversion: 120 |
2. Checking vxprint.
# vxprint -htg timdgDG NAME NCONFIG NLOG MINORS GROUP-IDST NAME STATE DM_CNT SPARE_CNT APPVOL_CNTDM NAME DEVICE TYPE PRIVLEN PUBLEN STATERV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRLRL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNKCO NAME CACHEVOL KSTATE STATEVT NAME RVG KSTATE STATE NVOLUMEV NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPEPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODESC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODEDC NAME PARENTVOL LOGVOLSP NAME SNAPVOL DCOEX NAME ASSOC VC PERMS MODE STATESR NAME KSTATEdg timdg default default 18000 1371483032.57.mtvat1000-c9l.mvw.spt.Veritas.comdm timdg01 ams_wms0_144 auto 65536 1931008 -dm timdg02 ams_wms0_145 auto 65536 1931008 -v vol01 - ENABLED ACTIVE 2097152 SELECT - fsgenpl vol01-01 vol01 ENABLED ACTIVE 2097152 CONCAT - RWsd timdg01-01 vol01-01 timdg01 0 1931008 0 ams_wms0_144 ENAsd 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.confaggregation.conf chroot devlink.tab format group initaliases clri dgroup.tab format.dat grpck initpipeamftab coreadm.conf driver_aliases fsck halt lost+foundauto_datastorm cron driver_classes fsdb hba.confauto_evidence dacf.conf dumpadm.conf fstyp hostname.bge0auto_home datemsk dumpdates fuser hostsauto_master dcopy esd.conf gabtab hosts-012312_133219autopush 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 IDdatadg1 enabled,shared,cds 1349716524.20.mtvat1000-c9l.mvw.spt.Veritas.comdatadg2 enabled,shared,cds 1349716609.22.mtvat1000-c9l.mvw.spt.Veritas.comtimdg02 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: timdgdgid: 1371484638.63.mtvat1000-c9l.mvw.spt.Veritas.comimport-id: 1024.62flags: cdsversion: 160 <<<<< Now we are at version 160# vxprint -htg timdgDG NAME NCONFIG NLOG MINORS GROUP-IDST NAME STATE DM_CNT SPARE_CNT APPVOL_CNTDM NAME DEVICE TYPE PRIVLEN PUBLEN STATERV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRLRL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNKCO NAME CACHEVOL KSTATE STATEVT NAME RVG KSTATE STATE NVOLUMEV NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPEPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODESC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODEDC NAME PARENTVOL LOGVOLSP NAME SNAPVOL DCOEX NAME ASSOC VC PERMS MODE STATESR NAME KSTATEdg timdg default default 10000 1371484638.63.mtvat1000-c9l.mvw.spt.Veritas.comdm timdg01 ams_wms0_144 auto 65536 1931008 -dm timdg02 ams_wms0_145 auto 65536 1931008 -v vol01 - ENABLED ACTIVE 2097152 SELECT - fsgenpl vol01-01 vol01 ENABLED ACTIVE 2097152 CONCAT - RWsd timdg01-01 vol01-01 timdg01 0 1931008 0 ams_wms0_144 ENAsd timdg02-01 vol01-01 timdg02 0 166144 1931008 ams_wms0_145 ENA # mount -f vxfs /dev/vx/dsk/timdg/vol01 /mnt# cd /mnt# lsTIMEZONE defaultrouter gabtabaggregation.conf device.tab gettyaliases devlink.tab gnome-vfs-mime-magicamftab dgroup.tab groupauto_datastorm driver_aliases grpckauto_evidence driver_classes haltauto_home dumpadm.conf hba.confauto_master dumpdates hostname.bge0autopush esd.conf hostscfgadm ff hosts-012312_133219chroot fmthard ima.confclri format inetd.confcoreadm.conf format.dat initcron fsck initpipedacf.conf fsdb lost+founddatemsk fstypdcopy 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.
Issue/Introduction
Additional Information
