HPUX 11i upgrades

[Patrick Wallek]

When doing your export of the VG's make sure you use the '-s' option as well so that the VGID gets written in the map file that gets created. You then specify the '-s' with vgimport and you do not have to specify each and every disk that is part of that VG. The vgimport scans all PV's for that VGID and imports all disks it finds.

# vgexport -p -v -s -m /var/tmp/vg??.map vg??

When importing:

# mkdir /dev/vg??
# mknod /dev/vg??/group c 64 0x0?0000
# vgimport -v -s -m /var/tmp/vg??.map vg??

[Bob_Vance]

Note about the "-s" :

If you use the -s option

and you are using distributed allocation

and you have dual HBAs for redundancy

*and* you are alternating primary (and secondary) paths between the HBAs to try to get some data transfer load balancing across the HBAs

(whew a lot of 'if's, but I run into this fairly often),

then the 'vgimport -s' will not keep your nice HBA load balancing scheme.
You will have to manually go back and create the alternating scheme.
However, it's simple to do -- simply vgreduce/vgextend every other primary path.

However, this points out a minor advantage of specifying the PVs directly on the vgimport, assuming that the device names are the same.

However, after a cold install, it's quite possible that the device names could change, in which case the "-s" option is a godsend.


hth
bv

[Mahesh Kumar Malik]

Hi Adam

Your approach seems to be OK. Please ensure there is no issue on the EMC model support on hp-ux 11i and system is patched with latest patch bundles

Regards
Mahesh