To list the files and directories included in a recovery image, use the list_expander command in the following way:

/opt/ignite/lbin/list_expander -f archive_content

where archive_content is the file that identifies keywords specifying inclusions and exclusions for the recovery image. It is the same archive_content file discussed in the "Recovery Image Creation Process" section above.

NOTE: The /var/opt/ignite/clients/client/recovery/archive_content file is overwritten whether a recovery image is successfully produced or not. Be sure the archive_content file matches the recovery image you are exploring.

Running list_expander without specifying -f archive_content causes a list of the essential recovery image files and directories to be listed.

You can also use list_expander to list disks and volume groups included in a recovery image by using the -doption:

/opt/ignite/lbin/list_expander -d -f archive_content Omitting the -f archive_content will cause the essential list to be displayed. The following is example list_expander -d output:

In?

dsk/vg

name

minor#

Associated disks

0

d

/dev/dsk/c0t3d0

 

 

1

v

/dev/vg00

0x00

/dev/dsk/c0t6d0

 

 

 

 

/dev/dsk/c0t4d0

0

v

/dev/vg01

0x01

/dev/dsk/c0t1d0

0

v

/dev/vg02

0x02

/dev/dsk/c0t2d0

The In? column shows, for each disk or volume group, if it will be:

2 = included in full (inc_entire specifies entire disk/volume group), or 1 = included in part (some files are included, some not), or 0 = not included at all (no files from this disk/volume group are included.)

The 0 means the disk or volume group will not be touched. The 1 or 2 means that the disk or volume group will be recreated and files from the recovery image will be restored during a recovery operation.

The dsk/vg column shows that the system has one whole disk (d) and three volume groups (v). The next column gives the names of the disks and volume groups.

NOTE: The following circumstance may cause list_expander to halt:

When processing information, list_expander uses the libc function ftw, see ftw(3C), to recursively descend the directory hierarchy.

When ftw encounters a directory containing a large number of files, all of the descendent files are processed recursively. This can cause stack size problems. For example, if the directory contained 400,000 files, the stack size must be at least 51.2 MB to support the number of recursive function calls (400,000 calls x 128 bytes/stack frame), since each ftw call allocates a stack frame of 128 bytes. In this case it is wise to allocate additional space - 64 MB is a better stack size choice.

If the stack size is not large enough, list_expander is killed due to a stack growth failure. To avoid this situation, you should configure the kernel tunable maxssiz accordingly. See the kctune(1M) manpage for more information on tuning kernel parameters.

The above information is based on the HP-UX 11i v1 ftw() libc function. The behavior of ftw() between releases or patch versions of HP-UX may change. Consider this information indicative of the potential setting required; it should not be considered authoritative.

The file system volume sizes in the recovery image can be modified when the recovery image is installed. By default, Ignite-UX ensures that there is 10 percent free space for each volume, and

System Recovery 195