HP 9000 Containers A.03.01 on HP Integrity Server Administrator Guide HP-UX 11i v3 (5900-3112, June 2013)

1. Do one of the following:
—In the case of file archive, copy the file to the HP-UX 11i v3 server (or make it visible via
an NFS-mount). Do not keep the archive in the root directory on the system.
Recover the archive:
$ /opt/HP9000-Containers/bin/hp9000_recover_image \
<hp9000_root> <image-file>
— In the case of tape archive, insert the tape into the Integrity server and present the tape to
the HP-UX 11i v3 system. For example, /dev/rtape/tape1_BEST.
$ /opt/HP9000-Containers/bin/hp9000_recover_image \
<hp9000_root> </dev/rtape/tape1_BEST>
2. Ignore any errors related to the recovery of the dev directory that are recorded in the log file.
5.3.5 Using other tools for recovery
IMPORTANT: If you use third-party tools for recovery, ensure that proper permissions and
ownership (UID and GID) are preserved. Some tools do not preserve setuid and setgid bits.
For example, verify permissions in the /usr/sbin/sendmail file to ensure that the setuid and
setgid bits are preserved.
5.3.6 Completing the recovery
After recovering the HP 9000 image:
• Manually verify whether all the basic directories (/etc, /home, /opt, /tmp,/usr, /var,
/stand) are recovered.
• Manually create the directories that are not copied, and assign proper ownership and
permissions.
For example,
$ mkdir <hp9000_root>/var/adm/crash
$ chmod 0755 <hp9000_root>/var/adm/crash
5.4 Creating HP 9000 classic container
To create HP 9000 classic container, add the hp9000cl template:
$ srp –add <srp_name> -t hp9000cl
The following configuration parameters must be set for HP 9000 classic container:
Auto start setting Controls whether or not the container must be started (through
an RC script) at the time of server boot.
HP 9000 root directory Specifies the root path <hp9000_root>, where HP 9000 files
are recovered.
Network parameters A static IP address is essential for the container. DHCP is
currently not supported.
Ensure that IP address, LAN interface, gateway IP, and subnet
mask are configured properly. The LAN interface can be either
private to the container or shared. The network configuration
is actually performed on the host system (not inside the
container).
If the HP 9000 server uses IPv4 address, use the same for HP
9000 container because the environment might not provide
complete IPv6 support.
5.4 Creating HP 9000 classic container 35