some lvol sizes increased in ignite recovery process

[Davor Bira?]

Hi,

I made bootable tape using
make_tape_recovery -x inc_entire=vg00 -a /dev/rmt/0mn -A

but during recovery proces some of lvols increased and on one server lvol took physical extents from second disk.

Any idea?

Kind regards,

Davor

[Patrick Wallek]

Did you do an interactive recovery or did you just let Ignite do the install without your intervention? I always do an interactive recovery for just this reason. It allows me to verify which disk(s) vg00 will use, what the LV sizes are, etc.

The Ignite install, without intervention should have put the VG/LVs back as they were, unless you changed the config file.

I can't think of a really good reason offhand that would cause the install to deviate from the original config.

[Massimo Bianchi]

I can think of only one reason: disks of different sizes.

On little disks base PE is 4Mb, but for larger disks base PE might be 8Mb or even 16Mb.

So the value for the logical volume is rounded up to the next entire value.


Is this your case ?

Massimo

[James R. Ferguson]

Hi Davor:

If you were recovering onto a larger physical disk this may occur, that is, if the physical extent size is larger. Ignite rounds up to an integer multiple of the PE extent size. For instance, a 500MB filesystem configured with a disk using 4MB physical extents uses 125 extents. If you attempt to depost that 500MB filesystem on a disk with 8MG extents, then 62.5 extents are required, so Ignite rounds the allocation upwards to 63 extents, increasing the filesystem from 500 to 504MB.

Regards!

...JRF...

[Jeff Schussele]

Hi Davor,

I suspect that this occurred due to your use of the -A parm.

From the man page:


-A Based on the files that are specified for inclusion, this
option identifies the disk(s) and/or volume group(s) that
contain these specified files and includes all files from
the disk(s)/vg(s) in the archive.

Create a system recovery tape with all the files/directories on the
disk(s)/volume group(s) containing the files specified by the default
essentials file list /opt/ignite/recovery/mnr_essentials or the user
defined version of this file, that replaces this file,
/var/opt/ignite/recovery/mnr_essentials.

make_tape_recovery -A

make_tape_recovery -s myserver -A

So I'd check the /opt/ignite/recovery/mnr_essentials file for clues.

BTW - I use the following:

make_tape_recovery -Ivx inc_entire=vg00

And always get the exact same layout on recovery.

HTH,
Jeff

[Davor Bira?]

Thing that solve may problem was new entry in /var/opt/ignite/clients/0x{LLA}/recovery//system_cfg:
cfg "HP-UX System Recovery"=TRUE
_hp_saved_detail_level="vfph"
#
# Variable assignments
#
init _hp_root_disk="52.4.0"
init _hp_root_grp_disks=2
init _hp_root_grp_striped="NO"
init _hp_pri_swap=131072KB
_hp_locale visible_if false
_hp_cfg_detail_level visible_if false
_hp_pri_swap visible_if false
_hp_min_swap visible_if false
_hp_disk_layout visible_if false
_hp_default_cur_lan_dev visible_if false
_hp_default_final_lan_dev visible_if false
_hp_keyboard visible_if false
_hp_root_disk visible_if false
_hp_boot_dev_path visible_if false
_hp_saved_detail_level visible_if false
_hp_root_grp_disks visible_if false
_hp_root_grp_striped visible_if false
init _hp_disk_layout="HP-UX save_config layout"
init _hp_ignore_sw_impact=1 <----- Insert this line here....



This should be done after preview mode.