only error is make_tape_recovery completed unsuccessfully

[Ratzie]

I run a backup from root cron,
30 18 * * 1 /home/bu/scripts/backup/os_make_tape_recovery.sh > /home/bu/log/os_boot_recovery_tape.`date +\%j`

The only error in the log is at the bottom, which says...
make_tape_recovery completed unsuccessfully

Roots mail says...
ERROR: The make_sys_image command failed. The system recovery archive will
not be created.


I am attaching my log output.
HP 11.00 with the pax update.

This is the script that runs...

MAKE_TAPE_RECOVERY=/opt/ignite/bin/make_tape_recovery

echo "OS make_tape_backup started at `date`."
echo ""
$MAKE_TAPE_RECOVERY -x inc_entire=vg00
echo ""
echo "OS make_tape_backup ended at `date`."

[Pete Randall]

First, make sure paths and variables and any other environment specifics are explicitly set in this script. Cron has a minimal environment with a restricted path and none of your variables will be available.


Pete

[G. Vrijhoeven]

Hi,

I would not worry about the Warnings:
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the back-up:
/tmp/cpu_perf.log
/tmp/sar_output.dat
/var/tmp/ign_configure/make_sys_image.log
/var/spool/cron/tmp/croutZAAa01095
/var/spool/cron/tmp/croutABAa01095

The message says it all. You only miss the files listed. This becouse they were deleted from the server before the ignite tape was finished and so these files will not be on the tape.
No problems.

Gideon

[T. M. Louah · Accepted solution]

Use mt and dd with lifls to verify the boot information on the tape, and use mt with tar to verify the data information on the tape.
# dd if=/dev/rmt/0mn of=bootimage bs=2k
# lifls -l bootimage
# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1
# tar tvf /dev/rmt/0mn

Cheers

[Bernhard Mueller]

Hi,

it is likely but not 100% sure that your archive is good.

check /home/sconway and remove or rename that file that starts with a non-printing character.

I had a case where there was a directory name consisting of only a single non-printing character which in turn prevented the system image from being writen completely....

Regards,
Bernhard

[Fabio Ettore]

Hi,

does "home/sconway/ mp\mts_user_lib.sql" file exist?
If yes try to find and remove it and re-launch make_tape_recovery.

Best regards,
Ettore

[Steven E. Protter]

somewhere in that log is a notation about a file that could not be backed up.

The message is higher up in the log, not next to the error code.

That file must be deleted, its got an illegal filename

if it says tmp/schmobagel.led

cd /tmp

rm schmo*

The illegal characters may or may not show up on a ls command.

I've been through this. If you check my recent questions in my profile you'll see my thread on the topic.


SEP