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

<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.
4.3.5 Using other tools for recovery archive
IMPORTANT: If you use third-party tools for recovery, ensure that proper permissions and
ownerships (UID or GID) are preserved. Some tools do not preserve setuid and setgid bits.
For example, verify permissions of the /usr/sbin/sendmail file to ensure that the setuid and
setgid bits are preserved.
4.3.6 Completing the recovery
After recovering the HP 9000 image:
1. Manually verify whether all the basic directories (/etc, /opt, /sbin, /usr, /var) are
recovered.
2. Create directories that are not recovered, and assign proper ownership and permissions to
them.
For example,
$ mkdir <hp9000_root>/var/adm/crash
$ chmod 0755 <hp9000_root>/var/adm/crash
$ chown root:root <hp9000_root>/var/adm/crash
3. If a third-party tool other than cpio, tar, and fbackup is used, restore the files that were
modified before the recovery.
$ cp –p /etc/passwd.backup /etc/passwd
$ cp –p /etc/group.backup /etc/group
$ cp –p /etc/nsswitch.conf.backup /etc/nsswitch.conf
4.4 Creating HP 9000 system container
This section explains the steps for creating an HP 9000 system container including configuring
PRM, adding hp9000sys template, and verifying configuration.
4.4.1 Configuring PRM
If you use PRM to allocate resources between multiple containers, choose whether FSS or PSET
must be used with cores. FSS provides better sizing and more flexibility, but might cause conflicts
when the application performs resource management internally (for example, when using database
resource managers). In the case of PSETs, the cores are reserved even when the container is down.
For FSS, the percentage entitlement is calculated as:
Number of shares assigned to a particular PRM Group
--------------------------------------------------- x 100
Sum of the shares assigned to all PRM Groups
4.4.2 Adding hp9000sys template
To create an HP 9000 system container, add the hp9000sys template:
$ srp –add <srp_name> -t hp9000sys
The container creation might take up to 30 minutes to complete.
Configuration parameters
Auto start setting Determines if the container must be automatically started at
system boot time. Answer no if the container is being created
on the primary node of an SG cluster and the container
package model is chosen.
4.4 Creating HP 9000 system container 23