make_sys_image command failed

[valcor]

Hello,
I have an itanium server running HP-UX v11.23
Is there an option in ignite during the make_net_recovery to archive the contents of a client via tar to another directory? I got to the part where it says:

*Archiving contents of client via tar to
/var/opt/ignite/recovery/arch_mnt/2007-06-26,15;35
gzip: stdout: File too large
ERROR: the gzip command failed (exit status 1)
ERROR: The make_sys_image command failed. The system recovery archive will not be created.

Instead of /var/opt/ignite/recovery/arch_mnt, can I point it to another directory, ie. /temp/recovery/arch_mnt?

Thanks in advance.

[Reshma Malusare]

Hi Valcor,

1] Ignite-UX creates a symbolic link between directories named after the clientâ s name and its MAC address. For example, if you had a system with a client name of "longs_peak" and a MAC address of "0x00306E4C9B54", the directories /var/opt/ignite/clients/0x00306E4C9B54 and /var/opt/ignite/clients/longs_peak would be symbolically linked.

2] You can specify what additional volume groups, directories, and files you want included, and what directories and files you want excluded. This is done using simple syntax in the client-specific content file, /var/opt/ignite/clients/client/recovery/archive_content, or by using command line options. You are not restricted to one or two volume groups. You can create a complete multi-volume group recovery image.

3] You can use the user interface (launched with the -i option to make_[tape|net]_recovery) to find out which volume groups and/or disks will be untouched, which will be partially restored, and which will be restored in full if the recovery image is used, based on the specifications in the mnr_essentials file and the archive_content file.

You can also use the user interface to edit the archive_content file and dynamically see the changes in the volume groups and disks that are affected.

Refer followinf document for details:

http://docs.hp.com/en/B2355-91049/ch11s02.html

Thanks & Regards
Reshma

[Radovan Rovny]

You don't have largefiles enabled on the filesystem

fsadm -F vxfs -o largefiles

[valcor]

Thanks for all your replies.

I did check my file system setting and found that it was not largefile enabled.

Will make necessary changes.

Thanks again.

[valcor]

Had to re-create file system to enable largefiles.
It works!

Thanks for all your help.