HP-UX 11i Version 2 Installation and Update Guide, September 2004
Table Of Contents
- 1 Welcome to HP-UX 11i Version 2
- 2 System Requirements for Cold-Installing and Updating
- 3 Choosing an Installation Method
- Supported Cold-Install Paths to HP-UX 11i v2
- Supported Update Paths to HP-UX 11i v2
- Deciding Which Method to Use
- Time to Complete a Cold Install or Update
- When to Cold-Install
- When to Update
- Additional Cold-Install Considerations
- Additional Update Considerations
- Requirement for Updating from HP-UX 11i v1.6 (B.11.22)
- Requirement for Updating from Earlier Releases of HP-UX 11i v2 (B.11.23)
- HP Service Partition Is Not Created During Update (Itanium-based Systems Only)
- Update-UX Contains a Default-Installed Selection File
- Update-UX Creates Two Backup Configurations
- Security Considerations
- Standard HP-UX Bundle Considerations
- Online Diagnostics
- Offline Diagnostics
- The Next Step
- 4 Preparing to Install or Update to HP-UX 11i v2
- 5 Cold-Installing HP-UX 11i v2
- 6 Updating to HP-UX 11i v2
- 7 Installing HP Applications and Patches
- 8 Verifying System Install or Update
- A Data Collection Tables
- B Known Problems and Troubleshooting
- C Controlling Memory Utilization of VxFS 3.5 on HP-UX
- D Software Distribution Media
- HP-UX 11i v2 Core Software Bundles
- HP-UX 11i v2 Always-Installed Patch Bundles
- HP-UX 11i v2 Always-Installed Software Bundles
- HP-UX 11i v2 Always-Installed Network and Mass Storage Drivers
- HP-UX 11i v2 Default-Installed Software Bundles
- HP-UX 11i v2 Selectable Software Bundles
- HP-UX 11i v2 Selectable Network Drivers

Preparing to Install or Update to HP-UX 11i v2
Backing Up Your System
Chapter 4 81
Using
make_net_recovery
The Ignite-UX server has the make_net_recovery command to create a
system recovery archive on another system on the network. The archive
created by make_net_recovery is specific to the system it was created
for and its identity includes host name, IP_address, networking
information, and so on. In the event of root disk failure, you use the
Ignite-UX server to restore the system by installing the recovery archive.
The contents of the system recovery archive always include all files and
directories that are essential to bringing up a functional system. This
essential list is predefined by make_net_recovery. You can run
make_net_recovery in its interactive mode to review the directories and
files that make up the essential list, and also to add or remove other data
from the archive on a disk/volume group, file, or directory basis.
For more information on using make_net_recovery, refer to the
make_net_recovery (1M) manpage or the Ignite-UX Administration
Guide.
Using make_tape_
recovery
The Ignite-UX server’s make_tape_recovery command creates a
bootable recovery tape for an LVM or whole disk file system while it is up
and running. When a system has a logical volume layout, the recovery
tape only includes data from the root volume group, plus data from any
non-root volume group containing the /usr directory.
You can run make_tape_recovery either on the Ignite-UX server or
locally on the system from which you are trying to make a recovery tape.
To create the bootable recovery tape, enter:
/opt/ignite/bin/make_tape_recovery -Av
where A specifies the entire root disk or volume group and v is for
verbose mode. Also, you can specify more than one volume group with
the -x option.
If you intend to use a tape drive other than the default (/dev/rmt/0m),
modify the command to point to the device you want to use, for example,
a tape drive at /dev/rmt/3mn:
/opt/ignite/bin/make_tape_recovery -Av -a /dev/rmt/3mn
To recover a failed system disk or volume group after a recovery tape has
been made, simply load the recovery tape, boot the system and interrupt
the boot sequence to redirect to the tape drive. Allow the install process
to complete. Do not intervene. The system will reboot and, because map
files for all associated volume groups have been saved on the tape, any