topic fbackup failure in Operating System - HP-UX

fbackup failure

peterchu — Mon, 23 Feb 2004 21:44:19 GMT

I have a backup job that run on the crontab ,
I tried to run the same job manually , it is successful , but if I run it on the crontab it is fail , the failure log as below:

-----------------------------------------------------------
Backup log generate from /usr/local/sbin/backup_job
Backup started on EDP : Tue Feb 24 23:45:01 EAT 2004
( fbackup -n -f /dev/rmt/0m -0 -u -g /usr/local/etc/br_daily -I /usr/local/log/b
r_index.24 -c /usr/local/etc/br_config )
fbackup(1004): session begins on Tue Feb 24 23:45:01 2004
fbackup(3038): output file /dev/rmt/0m is not a valid device file for backup
fbackup(3019): would you like to enter a new output file?
fbackup(3004): writer aborting
fbackup(1002): Backup did not complete : Reader or Writer process exit
/usr/local/log/br_index.24: No such file or directory
Backup FAILED ( exit code 2 ) on edp : Tue Feb 24 23:45:47 EAT 2004

I am wonder why it said the /dev/rmt/0m is not a valid device , as I can use it backup and restore usually , could suggest what is wrong ? thx.

Re: fbackup failure

Steven E. Protter — Mon, 23 Feb 2004 21:48:03 GMT

Seriously the usual cause of this is one of two things:

1) There is not a tape in the drive.
2) The tape in the drive is write protected.

Assuming it worked on the command line recently this means the device driver has not been hammered.

If it has insf -e will probably put it back.

SEP

Re: fbackup failure

Michael Tully — Mon, 23 Feb 2004 21:50:57 GMT

This error suggests that this could be a media issue, (write protected perhaps) or where the tape has actually ejected prior to the backup starting.

Re: fbackup failure

peterchu — Mon, 23 Feb 2004 22:02:08 GMT

I sure the tape is not write - protected ,

Re: fbackup failure

Michael Tully — Mon, 23 Feb 2004 22:15:15 GMT

If you can run the same job manually ... Can you run a simple 'tar' backup to the same designated tape and device.

Perhaps also a look at the latest patches for 'fbackup'. These are:

11i
PHCO_28988 fbackup/frecover
PHKL_29248 SCSI
PHKL_30259

Re: fbackup failure

T G Manikandan — Mon, 23 Feb 2004 22:21:57 GMT

I think that the tape drive is now connected to a different instance,which should point to a new device file.

It might be like the tape drive was connected and had a device file /dev/rmt/0m and now is pointing to a another file.

check
#ioscan -fnC tape

check whether it has taken /dev/rmt/1m

REvert

Re: fbackup failure

Steve Steel — Tue, 24 Feb 2004 04:22:45 GMT

Hi

1)lssf /dev/rmt/*

2)Check protection on files .. Are you backing up as root

3)FInd the tape drive in sam and use the options to remove and remake the device files

4)Check patch level

5)Remove and readd the cronjob

Steve Steel

Re: fbackup failure

Mark Grant — Tue, 24 Feb 2004 04:26:40 GMT

As a long shot, if you have recently added "set_san_safe" kernel paramter, only the no-rewind devices work.