Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

the directory is exported only to the individual client. To do this, log in to the system that holds
the recovery image (normally the Ignite-UX server).
For HP-UX 11i v3 systems:
• Edit the /etc/dfs/dfstab file on the source client.
• Append ,ro=target_client to the -o argument of the source client's line, where
target_client is a fully qualified client name.
• Run # shareall -F nfs
For HP-UX 11i v1 and 11i v2 systems:
• Edit the /etc/exports file on the source client.
• Append :target_client to the end of the source client's line, where target_client
is the hostname of the target system.
• Run # exportfs -av
See dfstab(4) or exportfs(4) for more information.
5. Boot the target client from the Ignite-UX server using any method you prefer. When you install
the system, you can select from the recovery configurations of the source system.
6. Change the system networking parameters for the client during the installation.
For additional information regarding system cloning, see the Successful System Cloning using
Ignite-UX white paper at
http://www.hp.com/go/ignite-ux-docs.
System Recovery Questions and Answers
Question:
Can I use a network recovery image if my system is not on the same subnet as the Ignite-UX server?
Yes, there are the commands make_boot_tape , make_ipf_tape, and make_media_install
that create minimal boot media for use by any client. The media contain just enough information
to boot a client and then connect to the Ignite-UX server where the tape, CD, or DVD was created.
If that is the server where the client’s recovery configuration files are stored, then the client can be
recovered.
It is not possible to boot all systems from a tape device. See “Tape Recovery With No Tape Boot
Support — Two-Step Media Recovery” (page 214).
If you initiate recovery tape creation from the Ignite-UX server, the server will warn you if the client
requires boot media. If you ignore this warning, misplace your boot media, or find that your media
are for the wrong Ignite-UX server, you can always create new boot media on the server you want
to use. There is no client-specific information on the media.
Notice that media created by make_boot_tape, make_ipf_tape, and make_media_install
are useful not only for recovery situations, but also for ordinary installations. If you do not want to
set up a boot helper for systems on a separate subnet than the Ignite-UX server, you can simply
create bootable media.
For more information, see Chapter 14 (page 177), make_boot_tape(1M), and make_ipf_tape(1M).
Other options include direct boot profiles (see “Direct Boot Profiles for Itanium-Based Systems”
(page 102)) and boot helpers (see “Ignite-UX bootp Boot Helper” (page 55)).
Question:
How can I change my setup so a network recovery image is available not only on the system for
which it was created, but also on other systems with very similar hardware?
System Recovery 217