Ignite-UX Administration Guide for HP-UX 11i (B3921-90080, November 2013)

2. Media Installation
This screen provides an option to switch the install source
from the default CD/DVD to a recovery tape. This is helpful
for those systems and for tape devices which do not support
booting from a tape.
[ ] CD/DVD Installation
[ * ] Boot from CD/DVD, Recover from Tape
[ OK ] [ cancel ] [ Help ]
3. Select Boot from CD/DVD, Recover from Tape and select OK to advance to the Tape Drive
Selection screen:
Tape Drive Selection
There are one or more tape drives detected on the system.
Insert your recovery tape into one of the drives and then
select that drive from the list below.
Use the <tab> and/or arrow keys to move to the desired TAPE device,
then press <Return/Enter> to select.
HW Path Device File Description
----------------------------------------------------------
[ 0/4/1/0.0x6.0x0 /dev/rmt/c6t6dOBEST HP_SDLT600 ]
4. Select the tape drive that contains the recovery image tape, then press Enter to start the
installation of the recovery image from the chosen tape drive.
Notes on Cloning Systems
Ignite-UX offers two main options for replicating (cloning) systems. The more flexible and complex
golden image method makes use of make_sys_image to create an archive of the source system,
followed by manually modifying configuration files to meet your needs. A much simpler (but less
flexible approach) uses make_[tape|net]_recovery. The pros and cons of each are described
here.
In each case, the source system that is used must contain software that is compatible with all clients.
This means that the version of HP-UX, patches, drivers, etc., must be sufficient for all systems
involved. This often requires installing a superset of software and drivers onto the source system
that will be used on all potential clients.
Using the make_sys_image method
Using the golden image method of creating an archive with make_sys_image and then modifying
Ignite-UX configuration files to reference the archive is very flexible, but somewhat time consuming.
The end result gives you:
• The ability to install systems from network or media from either an Ignite-UX server or local
clients.
• The ability to customize the process and tune it to accommodate many different situations.
• A "clean" system: log files and most remnants specific to the source system are removed.
• A rebuilt kernel containing just the drivers needed by the client’s hardware.
• The ability to install additional software or patches on top of the system archive from an SD
depot. This reduces the need to recreate the archive and enables you to add support for new
hardware that requires new patches or drivers without making a new archive.
See Chapter 11: “Golden Images”, for more information.
216 Recovery