Installing a system using another systems net recovery archive

[Jaris Detroye]

I have created a net archive on a server, next I boot my new system from the ignite server (This works fine). But, when the ignite GUI startsup it only shows me the default HP-UX install available, not the archive I just created. On other systems if I boot them from the ignite server it does show their own recovery archives available as an OS option.

Note: The recovery image is from a DIFFERENT server than the one I am attempting to restore it to.

Any suggestions as to how to make my recovery archive appear in the drop down box for OS selection?

[Steven E. Protter]

You can do it.

On th server, you'll have to modify the INDEX file and the other configuration files where they reference the archive.

You'll want to do the actual pull of the image interactively.

It may take a few tries before you tweak the configuration properly.

In /var/opt/ignite

find . -exec grep -l 'archive.gz' {} \; to get a listing of the configuration files to possibly modify.

SEP

[Ryan Hurst_1]

My knowledge is limited on this, but I believe the reason it's not showing up is because ignite will only show the archives who's lan ID info matches the lan ID of the client you're trying to boot.
I know there is a way around this, but I haven't figured it out yet. I'm sure though that this question has come up before and someone will point out how to do it.

[John Poff · Accepted solution]

Hi,

It's not hard to do. I had to go offsite and Ignite four boxes like this last week. Check out this Ignite admin doc:

http://docs.hp.com/hpux/onlinedocs/B2355-90810/B2355-90810.html

Under the 'System Recovery' chapter look for a section about 'Cloning a System Using make_net_recovery'. You pretty much just go into the /var/opt/ignite/clients directory and do a little shuffling, add a line to /etc/exports, and you are on your way. It works great.

JP

[Sridhar Bhaskarla]

Hi,

The trick is to create the client's directory on the ignite server. If the client is already up and running, then "adding the client" to the IUX server will take care of it. All you need to do is to copy the CINDEX and other files (as mentioned below by find and cpio) of the other system's directory into this system's directory. Once you have done it, just boot the client through ignite and it will take care of the rest.

If the system is not up and running, then you will have to do the above manually on the ignite server.
Say client to be cloned is systemA and the master image is from systemB

#cd /var/opt/ignite/clients
#mkdir 0x0xxxxxxxxxxx
(the physical address of the client to be cloned
#ln -s 0x0xxxxxxxxxxx systemA

Now copy CINDEX and recovery from systemB directory.

#find ./systemB CINDEX recovery | cpio -pdma
./systemA

#ll systemA

Make sure CINDEX and recovery directories are there.

Boot the system through ignite server. And it should give you choice to recover from the ignite image now.

-Sri