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

8.12.2 Exporting and importing an HP 9000 classic container
HP 9000 classic container shares a part of the file system with the HP-UX 11i v3 host on which it
resides. So, take the file system backup at system level, not at container level.
To backup the container configuration alone:
$ srp –export <srp_name> -b
To delete and reimport the container configuration:
$ srp –delete <srp_name> -b
$ srp –import –xfile <configuration export file>
8.12.3 Cloning an HP 9000 system container
Cloning a system container involves backing up the source container and creating a new container.
To backup the source container configuration and the file system, run:
$ srp –export <srp_name> ok_export_dirs=yes –b
Run the following command to use the exchange file to create a new container on the same host
or on a different host. You are prompted to enter new network parameters for the container:
$ srp –import <new_srp_name> -xfile <path of export file>
8.12.4 Backup applications with HP 9000 system containers
Backup applications can run inside HP 9000 system containers, but there are some limitations as
well. The limitations are as follows:
• The backup application cannot attempt tasks or commands (for example, applications related
to system administration) that are unsupported inside the container.
• Ignite-UX does not work inside HP 9000 containers.
• If compartment rules are used to restrict unsupported commands, read permissions on these
files are disabled inside an HP 9000 container. Therefore, an image, which includes command
directories (/sbin, /usr/bin, /usr/contrib/bin, /usr/lbin, and /usr/sbin) might
not contain the complete set of files.
• Do not recover a complete image from an HP 9000 server inside the container. If you recovered
an image, make sure that you reconfigure it before the next container start.
$ srp –replace <srp_name> -s init
Tape devices files can be copied to the container using the following command (if required):
$ srp –add <srp_name> -tune device=<tape device file>
Some backup applications (such as Legato Networker) can be configured to read /etc/fstab
and backup all configured file systems. To use this option, the mount points must be configured in
container local fstab (not in container pre-start fstab). However, the /usr and /var directories
are not supported in local fstab. For these file systems and container root directory, the backup
might have to be initiated separately from the host.
When using HP DP, run the disk agent from within the container and the media agent from the
global container. In addition, you might have to configure the disk agent in the global container
to backup the container root file system /var/hpsrp/<srp_name>.
If backup applications are used from the global container, and mounts are configured in the
container pre-start or local fstab file then, the container must be up when the backup is executed.
When using backup applications from the global container, synchronize UIDs and GIDs in all the
containers (including that of the global) on the system.
8.12 Backing up and cloning a container 57