Why did I loose vg02?

[Pete Randall]

Charles,

A quick review of the Release Notes ( http://www.docs.hp.com/en/IUX/whatsnew.html ) does not seem to indicate that this is something that has been addressed. I expect that you will continue to have to vgscan, vgimport and vgchange for these raw logical volumes. The one thing that might help is to run vgexport in preview mode, saving the map file on a filesystem that will get backed up:
vgexport -p -s -m /var/tmp/vg02.map /dev/vg02

Then, when it comes to time to rebuild, you should be able to just run your vgimport:
vgimport -s -m /var/tmp/vg02.map /dev/vg02

Good luck.


Pete

[Charles Holland]

Pete - I guess something like that is what I will have to do by hand. Eventhough it is done automatically for the other vg's (please see my original posting). Maybe I should call HP software support and raise the flag with them.

Regards

[A. Clay Stephenson]

My outbushwhack it approach would be to add a very small LVOL to vg02 (please tell me that you didn't use all the space in the VG), create a filesystem on it, and put the entry in /etc/fstab. The danger to automatically importing and activating this VG would occur in a ServiceGuard environment. My preference is to only use Ignite for vg00 and I'll take care of everything else including any needed vgimports.

[Charles Holland]

Sorry A Clay... sure did use it all....

Anyway update after upgrading to 6.1.44 verion of Ignite.

In? dsk/vg name minor# Associated disks/mountpoints
1 v /dev/vg00 0x00 /dev/dsk/c2t6d0 /dev/dsk/c2t5d0 /dev/dsk/c2t4d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /home 2
/dev/vg00/lvol6 /tmp 0
/dev/vg00/lvol8 /var 1
/dev/vg00/lvol5 /opt 2
/dev/vg00/lvol7 /usr 2
0 v /dev/vg01 0x01 /dev/dsk/c1t0d0 /dev/dsk/c9t0d0
/dev/vg01/lvol1 /sapdb 0
/dev/vg01/lvol2 /usr/sap/PRD 0
/dev/vg01/lvol3 /sapdb_backup0 0
0 v /dev/vg02 0x02 /dev/dsk/c1t1d0 /dev/dsk/c9t1d0 /dev/dsk/c1t2d0 /dev/dsk/c9t2d0 /dev/dsk/c1t3d0 /dev/dsk/c9t3d0 /dev/dsk/c1t4d0 /dev/dsk/c9t4d0 /dev/dsk/c1t5d0 /dev/dsk/c9t5d0 /dev/dsk/c1t6d0 /dev/dsk/c9t6d0 /dev/dsk/c1t7d0 /dev/dsk/c9t7d0 /dev/dsk/c1t8d0 /dev/dsk/c9t8d0 /dev/dsk/c1t9d0 /dev/dsk/c9t9d0
/dev/vg02/lvol01
/dev/vg02/lvol02
/dev/vg02/lvol03
/dev/vg02/lvol04
/dev/vg02/lvol05
/dev/vg02/lvol06
/dev/vg02/lvol07
/dev/vg02/lvol08
/dev/vg02/lvol09
/dev/vg02/lvol10
/dev/vg02/lvol11
/dev/vg02/lvol12
/dev/vg02/lvol13
/dev/vg02/lvol14
/dev/vg02/lvol15
/dev/vg02/lvol16
/dev/vg02/lvol17
/dev/vg02/lvol18
/dev/vg02/lvol19
/dev/vg02/lvol20
/dev/vg02/lvol21
/dev/vg02/lvol22
/dev/vg02/lvol23
/dev/vg02/lvol24
/dev/vg02/lvol25
/dev/vg02/lvol26
/dev/vg02/lvol27
/dev/vg02/lvol28
/dev/vg02/lvol29
/dev/vg02/lvol30
/dev/vg02/lvol31
/dev/vg02/lvol32
/dev/vg02/lvol33
/dev/vg02/lvol34
/dev/vg02/lvol1
/dev/vg02/lvol2
/dev/vg02/lvol3
/dev/vg02/lvol4
/dev/vg02/lvol5
/dev/vg02/lvol6
/dev/vg02/lvol7
/dev/vg02/lvol8
/dev/vg02/lvol9
* Checking Versions of Recovery Tools
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
80009D8D0FD/recovery/2005-06-23,20:00/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg01.mapfile /dev/vg01

* Backing Up Volume Group /dev/vg02
* /usr/sbin/vgcfgbackup /dev/vg02
* Creating Map Files for Volume Group /dev/vg02
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg02.mapfile /dev/vg02


Differences that I note right off hand.
1. Under the In? column there is no "-1" for vg02. Everything is either a "0" or a "1".
2. It did run a vgcfgbkup for vg00, vg01 AND vg02.

Now the next thing is to declare a failure and see how it goes on the recovery side.

Always forward

[Charles Holland]

Aparently resolution was to upgrade to 6.1.44 version of Ignite. When recovered the vg02 volumn groups were automatically recognized, recovered, and activated.

Thanks to all....