HP-UX HB v13.00 Ch-06 - Ignite-UX

HP-UX Handbook – Rev 13.00 Page 51 (of 58)
Chapter 06 Ignite-UX
October 29, 2013
Note: Because files like /etc/hosts and devices files are temporarily removed from the clients
system during the execution of make_sys_image, the system should not be in use !!!
1) Install the required operating system, patches and applications at the source system and
configure it to your needs.
2) Create the archive directory on the Ignite-UX server:
# /usr/bin/mkdir –p /var/opt/ignite/archives/Rel_B.xx.yy
3) Copy /opt/ignite/data/scripts/make_sys_image from the Ignite-UX Server to /tmp at
the source system and make it executable.
4) Run make_sys_image on the source system with following options:
# /opt/ignite/data/scripts/make_sys_image –v \
-f <script with files or directories to exclude> \
-d <directory to place the archive> \
-s <ip-address of system to place the archive>
for example
# /opt/ignite/data/scripts/make_sys_image -v -f /tmp/exclude \
-d /var/opt/ignite/archives/Rel_B.11.23 -s 10.10.3.4
-f: It is possible to list single files. For further information please see the man page of
make_sys_image. In this example, the directories /space and /export will not be
saved into the Golden System Image. The exclude file has following format:
# /usr/bin/cat exclude
+ ONLY NO_ARCHIVE
/space
/export
-d : The chosen directory must have enough space. The Image will be created as a gnuzip
file and is about half the size of the data to be saved. The directory must be exported via
NFS.
-s: Instead of the Ignite-UX server IP, the local IP can be used for creating the System Image
locally. Then copy the archive named <hostname>.gz later to the Ignite-UX or another
archive server.
Optionally verify the image contents with:
# gzcat <hostname>.gz | pax –v | grep <file_name>