Move boot disk.

[Harald Doevenspeck]

I am facing following problem.

We have a machine with several vpar's. These are booted from the SAN.

Now we would like to move on of the vpar's to another machine. One of the idea's is :
- shutdown vpar on machine 1.
- make all disk visible to machine 2 (on SAN-level).
- create a new vpar in machine 2.
- boot new vpar from old boot disk.
- make necessary changes to other things (vg's, etc).

However we don't manage to boot the new vpar from the old boot disk.

We have tried several things, eg :
vparboot -p esap132 -B 0/0/4/1/0/4/0.12.14.0.35.2.0

Then we get :
MON> Alternate boot path not found.
Internal error in setting up vPars variables.
"esap132" load failed.


The servers are Integrity servers (with HPUX), which makes things more complicated since they have an extra boot layer, the EFI-layer.

Maybe it will be faster to use an Ignite backup ?

Any ideas how best to do this ?

[Jaime Bolanos Rojas.]

Harold,

Maybe somewhat somehow you can make this work, what came to my mind is the first place is that it does not look like the supported and tested way.

If it was me I would go with the backup, even thought you might get plenty of options in this forum.

Regards,

Jaime.

[Tim Nelson]

Use Ignite to build the new server with the image of the old.

If something goes awry you can always revert back.

[Torsten.]

Hi,

if the hardware path is changed, you need to adjust the LVM config.

Boot the first vPar to LM mode

MON> vparload -p winona2 -o "-lm"

and export/import the VG and reboot.
Once the first vPar is started, do the same for the other vpars from the running one:

winona1# vparboot -p winona2 -o "-lm"