LATEST IGNITE RELEASE

[uspfoms]

Installed Ignite version B.4.1
from Dec 2002 Application CD,
Appeared to run ok (made DLT tape)Using this command-- make_tape_recovery -AvI
Where is the log file at ?
Also release notes say two PAX
patches must be installed. Do I need these if all I'm using it for is to make a recovery tape for one system, the one it's installed on ?

[Pete Randall]

logs are in /var/opt/ignite/logs.

The pax patches deal with large files and long file names (and possibly other things). They're relatively painless to apply and probably a good idea.

Pete

[Marco Santerre]

the log file file is located at /var/opt/ignite/logs/makrec.log1

[Robert-Jan Goossens]

Hi,

If you only make make_tape_recovery the answer is no.

When Ignite-UX creates a system archive via make_sys_image, it uses the pax(1) utility. You should install the latest pax patch on the system where you will be creating your archive.

Obtain the appropriate patch from HP's IT Resource Center. Select: Maintenance and Support -> Individual Patches. A brief registration is required.

http://www.software.hp.com/products/IUX/index.html

[uspfoms]

I have a makrec.log1 and a makrec.log2 log1 is from the previous version I used and contains good info. Log2
is from current version and only contains a list of file names, where is the info that scrolled across as Ignite program was executing ?

[Marco Santerre]

My question for you is did you run the make_recovery manually or through a cron? If you ran it through cron and didn't redirect your output into a log file than the messages that you normally see with Ignite are gone.

[uspfoms]

I ran it from the command line, as much info is displayed it seems like it should log it somewhere.

Thanks

[Cheryl Griffin]

Just a clarification: you said it requires two pax patches, but note that they are for different os versions, so really you only need the one that applies to your system.

# uname -r

The two patches are:
11.11 patch is PHCO_26422
11.00 patch is PHCO_25418

Cheryl

[uspfoms]

Cheryl, Is previous response about not needing the patch for a standalone system correct ? Also why is there not a complete log file ?

Thanks

[Patrick Wallek]

You do need the pax patch, no matter what you are doing. The tape is created with pax.

If you run the command from the command line, the stuff you see on the screen will NOT be written to a log file.

If you want it written do something like the following:

# /opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -I -v -x inc_entire=vg00 > /tmp/ignite.log 2>&1

The above will run the make_tape_recovery and write everything, standard out and standard error, to the file /tmp/ignite.log

You could also use the above syntax if you were running the job through cron. You could then have your cron job e-mail you the output by adding the following line after the make_tape_recovery command:

mailx -s "make_tape_recovery results" yourname@abc.com < /tmp/ignite.log

[Cheryl Griffin · Accepted solution]

pax is what writes the archive out, similar to tar. The patch is needed because there have been changes to pax that affect how files are written to tape. For example you want pax to write the user id and group id correctly to tape.

So if your system is 11.00, apply PHCO_25418. Or if your system is 11.11 apply PHCO_26422.

Log files for make_tape_recovery:
If executed locally, the recovery.log and flist logs will be located in
/var/opt/ignite/recovery/.

If executed remotely via the Ignite server GUI, these logs will be located on the server in
/var/opt/ignite/clients/0x{LLA}/recovery/ (where LLA is the client address)

Filenames:
recovery.log = progress and error log
flist = archive content log
/var/opt/ignite/local/install.log = tape restoration log

If your output is truncated or incomplete, was there an error that may have displayed or did the command hang? Is the filesystem full by chance?
Cheryl

[Pete Randall]

My apologies, Cheryl is right of course. The log file location I pointed out is from the older versions of Ignite.

Pete

[Robert-Jan Goossens]

Hi,

My apologies for confusing you about the pax patches.

Robert-Jan.