Ignite warnings

[Andrew_adm]

Hi everyone,
I have done one make_net_recovery and other one make_tape_recovery over a prodcution system and its backup system, the fact is ignite reports some warnings that i dont know if could suppress them, they are that follows:
WARNING: File 'vgusers' in archive_content list not found, or too big for pax
to handle. Skipping.
WARNING: File 'vgexports' in archive_content list not found, or too big for pax
to handle. Skipping.
WARNING: list_expander returned a warning,please check the log file.
WARNING: File 'vgusers' in archive_content list not found, or too big for pax
to handle. Skipping.
WARNING: File 'vgexports' in archive_content list not found, or too big for pax
to handle. Skipping.
The command that i type was:
VG´s vgusers, vgexports were excluded through -x exclude=VGname option, i just wanted to save vg00 with -x inc_entire
option and i did so. My question is, can i suppress these warnings?. On ignite server it reports the make_net_recovery was successfully completed without warnings, but within log appears these messages. About make_tape_recovery, it was completed too with the same warnings. (VG´s excluded and included on the two servers were the same).
Regards.

[Steven E. Protter]

Shalom,

This is potentially a problem.

Possbility 1.
Your pax version can't handle files bigger than 2 GB. Therefore it skips file bigger than 2 GB. You can patch pax to fix this but the utility pax_iux which unpacks pax archives may not be able to unpack the archive on a restore.

Check for the existance of the files. If they do not exist its probably not an issue. If they exist and are bigger than 2 GB then ask youself why are they included in the archive.

Generally I use Ignite to create a bootable/installable image of vg00. I don't include other volume groups or open databases because they won't work after the Ignite image anyway.

SEP

[Andrew_adm]

Aha, i understand, but pax reports these messages about vgusers and vgexports and these were excluded, the unique vg included was vg00, thats the cause i dont know why it occurs.

[IT_2007]

may be missing some patches? what version of Ignite-UX are you running? Also tell us what OS version and model are you running on?

[Bill Hassell]

The mssage syas:

File 'vgusers' ...

Although this is the name of a volume group, I would not expect an error message to say File unless it was referring to a real file. Do you have an accidental file in vg00 called vgusers (and vgexports)? There is no reason to exclude these VGs because -x inc_entire vg00 completely unselects any other VGs. Try something like this:

make_tape_recovery -I -v -x inc_entire=vg00 -a /dev/rmt/whatever