errors when running make_tape_recovery

[James Ellis_1]

I have Ignite 4.3 on 11.0 system.

When executing make_tape_recovery, I get these errors show up at the bottom of /var/opt/ignite/recovery/latest/recovery.log:

NOTE: The following files in the list of files that were on the system, but they are no longer present. These files are not included in the backup:
/var/tmp/ign_configure/make_sys_image.log
/var/spool/cron/tmp/croutISAa01314
/var/spool/cron/tmp/croutFSAa01314

Question: Are these files supposed to be there? It may have been removed, although I don't remember it being removed. Can I create a file called make_sys_image.log with root and correct permission? These are all under .../tmp...so I presume these are not that important files?

Thanks for your inputs.

[Pete Randall]

James,

The /var/spool/cron files are inconsequential and can be ignored. I'm not so sure about the make_sys_image.log. I would suggest rerunning the make_tape_recovery to see if you get that same file missing. It seems like it should be created by ignite and it shouldn't disappear!


Pete

[Chris Wilshaw]

These are nothing to worry about - they're temporary files that have been created during the process.

The first is created by Ignite itself, the second and third would have contained cron job details which the associated jobs were running.

[Bill Hassell]

On a running systm, you will always have some temp files that are removed sometime during the backup. This is true for any backup tool since there is such a lkong delay between making a list for backup until thwe file is actually copied to tape.

[James Ellis_1]

Chris,

That is what I figured, but why is this reporting these on one of the server, and not on other servers. For example, all of the servers have a bunch of croutxxxxx files, but this one server is reporting a missing of two of these files?

Bill/Pete, the make_sys_image.log on one of my other HP server is present, and contains this line:

644 root sys make_sys_image.log (size 49)

#more make_sys_image.log shows

08/03/04 14:46:04 EDT END make_sys_image

Nothing real important, but apparently if this file is present, the system will not complain. If this file is a temporary file, this would not be important, but I am wondering why make_tape_recovery is looking for this file in the first place? My question: Should this file always be present?

Thanks.

[Bill Hassell · Accepted solution]

make_tape_recovery is just running pax and is given the list of files at the start. pax doesn't have an index like fbackup so it just reads the list to backup as it goes along. The croutXXXX files are created and removed by cron automatically, perhaps several times during the backup window. The make_sys_image.log file may have been there when the list was passed to pax and removed somewhere along the way.

In any case, you can always expect some temp files to be missing during the backup, just as if you used fbackup.

[James Ellis_1]

Bill,

Thanks for your help. You replied with:

The make_sys_image.log file may have been there when the list was passed to pax and removed somewhere along the way.

Is it important to have the make_sys_image.log file? If I wanted to have it there, so that no errors are encountered with make_tape_recovery execution, can I just create /var/tmp/ign_configure/make_sys_image.log with the correct permissions and ownership?

Thanks,
Jim

[Bill Hassell]

Actually, the important file is /var/opt/ignite/recovery/latest/recovery.log rather than /var/tmp/ign_configure/make_sys_image.log. In my Ignite script, the make_sys_image logfile is always missing but make_tape_recovery doesn't return an error code. I think that this file exists after make_tape_recovery runs only if there was a problem with the make_sys_recovery portion of MTR. Everything you see on the screen with the -v option in MTR is logged in /var/opt/ignite/recovery/latest/recovery.log. In fact, the files related to the most recent MTR are in /var/opt/ignite/recovery/latest which is actually a symlink to the most recent date in /var/opt/ignite/recovery/.