Using Ignite to build a new server

[Rose Marie Mansell]

I have two HPUX 11.23 Itanium rx2660 servers in house that are identical. The plan is for one to be dedicated for development and the other for production. Both servers are attached to an EVA5000.

I have been using make_tape_recovery for years and has saved me many times on HPUX system recoveries.

I have built and customized my new development HPUX server and have installed various required applications for our environment on it.

I have read over the documents for cloning and igniting servers but find the material a bit overwhelming and somewhat confusing.

My concerns are if I use the make_tape_recovery from my development server is that I need to make certain that server name, ip and whatever else needs to be changed so that it reflects the profile of the production server.

As is with any sys admin time is not on my side and your assistance and guidance would be greatly appreciated.

[James R. Ferguson]

Hi Rose Marie:

Using an Ignite 'make_tape_recovery' image to clone a server as you desire, works very well.

For you target server, boot from the Ignite tape; choose Install -> Advanced Installation Mode.

You will be able to tailor the filesystem sizes should you wish, and most importantly you will be able to set your network (and hostname) parameters. I prefer to toggle the "Ask at first boot" method. Ignite will run and reboot when finished. You will then be presented with an execution of '/sbin/set_parms' from which you will be prompted for all of your networking parameters.

Regards!

...JRF...

[Steven E. Protter]

Shalom,

In a two server environment, if both servers are intended to be exactly the same from the boot perspective, make_tape_recovery is about your only option.

You can simply to replicate, boot the server off tape, and intervene at the ignite prompt and set the root password, hostname and network information.

In an environment with more servers you might want to consider having an Ignite server, which with enough storage will permit you other server build options.

SEP

[Wim Rombauts]

There still will be som ejob to do that is not handled by Ignite :
- Regenerate SSH keys, unless you want bot systems to have the same security keys.
- Modify /etc/hosts
- You applications may have config files with IP-addresses and server names.
- Your swinstall security (/var/adm/sw/security/_ACL) needs to be modified for the new hostname.

And I probably forget a few things here.

Still, Ignite is your best bet, but don't think it will be install-and-go, there will be some post-processing.

[Rose Marie Mansell]

Thank you all for the great input. Thanks for the list of items to check to change for server name, ip, and ssh. Do, I need to worry about mac address or serial number or anything else like that that would not be readily apparent to a novice like me at doing this? It would be nice if HP would have a list of all the tidbit items to review that would need changing when cloning a system.