Ignite-UX Server

[Andrew Luis Arruza]

Need some help with Ignite. Do I have to have Ignite running on each server that I am using to use the make_net_recovery?
I am using one server to make_net_recovery for about 15 others.
I have also just downloaded the latest version of Ignite-UX; B.3.3, will that have to be installed on each server?
I WILL gladly assign points for any/all help.
Thanks,
Andy

[Peggy Fong]

You do not need to run Ignite on all your other servers. But you will need some software (at least one program....) Sorry I don't know which piece of the Ignite software you need.

You may already have this info but here is the website for Ignite/UX which will have the latest info:


We will need a portion of the HP Ignite product to obtain the software (make_recovery command) required to build a bootable backup tape of the root volume group. This can also be used to clone systems that have the same os configuration with patches and security setup already.

You can get the latest version of Ignite from HP's web site. The software is free and you can get documentation for Ignite, as well as instructions downloading and copying into a depot. The software is located at:

http://www.software.hp.com/products/IUX

I'm sure someone else will have the program you need on each server to create the archive and get it back to your ignite server.

Best of luck.
Peg

[Sprint Unix Team]

if u want to have an image for building servers in future, you may have to use the make_sys_image command.

To have a recovery tape you can use make_net_recovery. I would suggest to use one ignite server to do archives of all boxes and store it in a seperate file system.

In event of a server crash, you can boot from the network using the ignite server and recover the system instead of looking for tapes.

Hope this answers your question

[George A Bodnar · Accepted solution]

Yes you do need the Ignite software on each node, but you can set this up to automatically install (and upgrade) on each client node using the following in a script:

# Either install the software or upgrade Ignite if needed
/opt/ignite/lbin/check_version -s ${SERVER}
if [ $? -ne 0 ]
then echo "Installing or upgrading Ignite software\n"
swinstall -s ${SERVER}:/var/opt/ignite/depots/recovery_cmds '*'
if [ $? -ne 0 ]
then echo "Error updating software `date` EOJ"
exit 1
fi
fi

This requires you to create the Ignite depot using the following command:

pkg_rec_depot -f

The -f option gives you full Ignite. If you do this without -f you get just enough to do the network ignite, but not enough if you do want to do an Ignite to tape.

Also will need to configure the NFS mount points on the server which simply means exporting /var/opt/ignite/clients as rw to the servers that need access as well as /var/opt/ignite/recovery/archive/$SERVER for each server rw as well.

We use this for about 2 dozen servers and so far it has worked very well. Note most of this stuff can be done via the GUI, but we have cron type jobs which is why I know the command line stuff.

Hope this helps.

[Carl Zabel]

If you add the clients to your server via the gui and then run make_net_recovery from the server gui the server will automatically install only the software the client needs.

If you do run all of your net recoveries via the server gui make sure and umount the server directories from the client after the recovery is finished. I have had these nfs mounts hang and ultimately had to reboot the client and the server. Running the recovery via a script thru cron from the client has not produced this problem and unmounts the server directories cleanly.