Ignite for Vpar restoration

[pa8700]

I have two vpars.Onee of them crashed.I have the ignite backup of the other servwer.Can i restore it to the crashed one.

Pls help sombody with the steps needed.

[Steven E. Protter]

Shalom,

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02015658/c02015658.pdf (BSC link updated by admin)

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01943931/c01943931.pdf (BSC link updated by admin)

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01942669/c01942669.pdf (BSC link updated by admin)

SEP

[Johnson Punniyalingam]

You just need to boot the failed vpar and point the boot kernel to your Ignite-UX Server,

for PA-RISC:
# vparboot -p -I xx.xx.xx.xx,/opt/ignite/boot/WINSTALL


I don't know what version of vpar you used, but check this documentation, chapter 10, "network and tape recovery":
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01940910/c01940910.pdf (BSC link updated by admin)


Thanks,
Johnson

[Johnson Punniyalingam]

Take care because in the latests versions of ignite you can't define a route to the server, then a good idea is to use a cross ethernet between the lan of your ignite server and one IO of the vpar, then use vparload -p partitionname -I


Thanks,
Johnson

[Fabio Ettore]

Hi,

so I understand the vpar which crashed didn't come up anymore, so you've decided to reinstall it.
I'd try to understand the reason of that, if the problem was a kernel problem and you did everything to recover that unsuccessfully then it makes sense to reinstall, otherwise if the problem was a disk of vg00 problem (or everything else of HW) I don't think reinstall the system will solve the problem.

Have you done a minimum troubleshooting before to decide to reinstall the system starting from the reason the system cannot come up again (I suppose you have this condition)? If so what have you checked?

If you're interested please post some further details in order to help you to avoid (if possible) to reinstall the system.

Best regards,
Fabio

[pa8700]

ya its actually a test server.
its not commint to level 3.am able to boot to level1.but when i take it to 3 am not getting the colsole.saying forking too many process

[Torsten.]

Is your ignite backup on tape or server archive? For tape restore you need to have vPar version 3.03 for pa-risc minimum.

You need to add the tape path to your vPar configuration

vparmodify ... -a io:.....:TAPE
and use this device with vparboot:

vparboot .... -B TAPE

[pa8700]

I dont have the archive of the same sever.But I have a network archive of another vpar of the same npar.

I am plannng to restore that one to the crashed one.

[sujit kumar singh]

Hi


NO issues you can do that over network from the Network archive image as on the Ignite server that is your other VPAR or on some other NPAR as the case may be. From the booted / running VPAR do a vaprboot as suggested by Johnson.


You can also have a look at the VPAR Admin guide here.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02029116/c02029116.pdf (BSC link updated by admin)

Depending on the underlying NPAR is an IA or PA follow the PDF Steps appropriately. page nos 121 and 287.
regards
sujit

[Fabio Ettore · Accepted solution]

Hi,

>ya its actually a test server.
its not commint to level 3.am able to boot to level1.but when i take it to 3 am not getting the colsole.saying forking too many process


it's most likely something wrong is into /etc/rc.config.d/*, some file shouldn't be there. Check in this way:

- go on run level 1 and do:
vi /sbin/rc

(insert set -x on top)

- run the /sbin/rc:
/sbin/rc

You'll have a long output with reasons the boot isn't completeing correctly.
Consider that the problem could be even a bad character into files under /etc/rc.config.d, I saw that many times into netconf for example.

Of course last resort should be to reinstall.

Good luck...

Best regards,
Fabio