Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

5 Recovery (make_tape_recovery and
make_net_recovery)
Frequently asked questions
Following are the frequently asked questions in various modes of recovery, which is a compilation
of all the available feedback from the users.
We tried running the recovery system option from a client booted in Ignite-UX, which
generated errors. What files need to be accessible for tftp?
Only /opt/ignite and /var/opt/ignite are needed for tftp access.
How do I duplicate a tape made with make_tape_recovery?
For this information, see copy_boot_tape(1M). For information about how to copy a recovery tape
for an HP Integrity server, see How do I duplicate a recovery tape from an HP Integrity server? in
HPSC.
How do I deal with hot-swappable disk devices during recovery?
Ignite-UX only supports hot-swappable disks that are completely installed and present when creating
a recovery image. Proper software and hardware procedures must be used for hot swap disk
removal or replacement before or after recovery, but not during recovery. LVM command lvlnboot
used by save_config does not work when a disk is removed and the system is in this transitional
state. If this command is not working, then recovery has no chance of succeeding. See the
information about SAS disks in Ignite-UX Release Notes for Version C.6.8.
What is the maximum amount of data that a make_tape_recovery tape can hold?
A make_tape_recovery tape can hold as much data as will fit on the tape. If
make_tape_recovery is run in the foreground it prompts for more tapes if they are necessary.
NOTE: To include files larger than 2 GB but less than 8 GB, you might need to install patches.
On HP-UX 11.11 you must have PHCO_28414 or later installed. On HP-UX B.11.23 you must
have PHCO_31634 or later installed. Otherwise, files will be limited to being less than 4 GB in
size.
How do I boot correctly from a recovery tape on a V-class system?
When booting from a recovery tape on a V-class system using an incorrect boot string, it is possible
that the following errors are generated:
Command: bo 4/2/0.1.0 VINSTALL Device : 4/2/0.1.0
File : hpux Arguments : hpux VINSTALL
Loading : hpux.....175984bytes Loaded
110448 + 65536 + 865264 start 0xd01c88
Boot
:tape(4/2/0.1.0;0)VINSTALL
tape(4/2/0.1.0;0)VINSTALL:cannot open, or executable Exec
failed : No such file or directory
The correct method for booting any kernel from a tape is to add a colon (:) to the start of the kernel
name. The colon indicates the bootloader reads the kernel from the LIF at the start of the media.
Without the colon, the bootloader attempts other methods to read the kernel, but it does not attempt
22 Recovery (make_tape_recovery and make_net_recovery)