Logical volumes kept upgrade to hp-ux11

[Greg Roberts]

I'm upgrading from hp-ux 10.20 to 11. I have a very large Orcale data base on 9 harddrives and an ftp site spanning 4 harddrives as a logical disk. I know the Orcale will be hosed but question is since I have 20 harddrives attached with "stuff" on them will I lose the disks when I upgrade (actually doing a new install)??? I'll install the OS on a main drive broken into logicals. Will the data on the ftp logical drive (4 harddrives linked) be lost?? Is there something I need to do during install to kept logical drives intact or let the system know they exsist??? I will be doing a new install over the old system to run other new installed programs but need to keep data on 19 other harddrives intact to sort out later.
Thanks

[Patrick Wallek · Accepted solution]

All the data on your non-vg00 volume groups will not be touched when you do the install. What will want to do prior to installing the new OS is a 'vgexport -p -m mapfilename -v -s /dev/vg??' for all of the volume groups on your system. Then take the mapfile and put it on a tape or ftp it to your PC or another system so that you can get it back on the system after you install the new version of the OS. Once it is installed you can do the mknod to make the /dev/vg??/group file and then do a 'vgimport -m mapfilename -v -s /dev/vg??' for all the volume groups. This should import all your volume groups. You then activate them and you can remount all the lvols.

I would make sure that you have a good backup of your system and make sure you have copies of all critical systems files (/etc/fstab, /etc/hosts, /etc/passwd, /etc/group, /etc/rc.config.d/netconf, output from bdf, output from vgdisplay and lvdisplay for all VGs and LVs and whatever else you think you need). Do an ignite backup (make_recovery) of the system before the upgrade if you can.

[Joseph C. Denman]

with all that data, be sure to get a good ignite tape prior to upgrade!!!

Good luck.


...jcd...

[Bill Hassell]

The LVM headers on the disks will allow SAM to add the disk groups back again, even if you forgot to use vgexport. This works importing LVM from 9.04 as well as any version of 10.xx. Just go into SAM, select disks, then volume groups, then Actions for Import...

SAM will scan all the attached disks then group all the volumes it hasn't seen before and groups them into the original collections of disks. Now SAM has no way to guess what the volume group name is so you have to supply the /dev/vg. All the lvols are retained using the default names (lvol1, lvol2,, lvol3...) but you can rename these with a simple mv command.