Why is this happen.

[Sachin Patel]

Hi All,
I installed Ignite server on 11.00 OS.
Add client (N-class). I did archive on to one of the disk on server (make_net_recovery).
Then reboot the client from server It reboot the client using bootsys -a. It reboots and start from /stand/WINSTALL. I didn't want that so I boot the system in single user check the content of /stand. Found vmunix so rename the WINSTALL and W*.
Reboot the system and it is screw up.

I had the tape from make_boot_tape so system is up and running within a 45 minutes. But how can I reverse the step.

We do not clone anything here So my main goal is to have archive of all my big servers and anything goes wrong then I can restore it back within couple hours.

Sachin

[Eileen Millen]

To restore across the network, you can interrupt the boot and enter
boot lan.ip_addres_of_Ignite_server install

[Sachin Patel]

Hi
System has no such option. It don't even know what is
command>sea lan

Sachin

[Alex_17]

Hi,
try reading document B2355-90738.pdf from www.docs.hp.com (page 60). Maybe helps you.

Good luck.

[Michael Roberts_3 · Accepted solution]

When you run bootsys it copies a program to the client in /tmp/bootsys_prep and also adds a start up script /sbin/rc2.d/S203clean_bsys. If you interrupt the boot sequence and manualy boot from /stand/vmunix
ISL>hpux /stand/vmunix
into at least run state 2, the rc script will undo the changes to the AUTO file in the boot lif.

If you manually boot /stand/vmunix in single user mode then you can mount /usr (to get access to the lif* commands)
and run /tmp/bootsys_prep -u. This will also undo the changes done by bootsys.