Boot on SAN migration in vpar environnement.

[Christ 33]

Boot on SAN migration in vpar environnement.


Hi all,

I am looking for some information.
I have an rp8420 server with 3 vpar. All the vpar are booting on an EMC SAN. We need to transfer this boot on SAN on an Netapp disc system.

I try with mirror Unix to copy Vg00 from EMC to Netapp and reboot from Netapp.
This works fine.

I want to know if I can move, reboot each vpar independently, without any interact between them, or, if there is different commands for the vpar manager. In this case, do we need to shutdown all the vpar to reboot the partition manager?

How to copy the vpmon ?
Is it independent, or it will be copied with the first vpar?
In this case, how to identify with which vpar, is it linked?

Many thanks for your help.

Christian

[Zinky · Accepted solution]

Peace with thee Christian,

Why don't you just use mirroring?

First:

pvcreate -fb your new NetAPP boot disk
mkboot ---
vgextend..
lvextend...

Then change your Boot PRI to your NETAPP LUn...

BUT, check first if a NetApp LUN is supported as a SAN Boot device. HP has a document that lists what are the supported SAN Arrays that HP-UX can use as boot disks/luns.
See: javascript:openExternal('http://docs.hp.com/en/7408/HPUXSANBootWP_final_v2_update.pdf?jumpid=reg_R1002_USEN')

[Torsten.]

Hi,

first you should check if your new array is supported as a boot device, e.g. with this matrix:

http://www.hp.com/products1/serverconnectivity/mass_storage_devices.html

If you mirror your vg00, you will also mirror the vpmon, because it is in /stand.
All vpmons will synchronize by themself.

To get rid of your "original" vpmon located on the old disks, you should reboot the whole nPar, I guess.

[Zinky]

http://www.hp.com/products1/serverconnectivity/mass_storage_devices.html and it appears NetApp is not.

So try/use at your own risk.

[Christ 33]

Thanks for your answers,

I used Hp-ux mirroring to make my boot on san migration.