fbackup problem

[lin.chen]

when I use fbackup,I will get following error message:
br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1421): no history is available for graph file /var/sam/graphFDAa21681 (below level 0)
fbackup(1004): session begins on Fri May 18 15:53:18 2007
fbackup(3038): output file /dev/rmt/c5t3d0BEST is not a valid device file for backup
fbackup(3019): would you like to enter a new output file?
n
fbackup(3022): would you like to continue this session?

and the tape drive is not HP's.it is Certance ultrium2.
How can i fix it?
thanks a lot!

[DCE]

Did the tape drive ever work with this system? HP requires certain microcodes on the devices - is the Certance ultrium2 certified to work on a HP system?

Do an ioscan -fnC tape to see if /dev/rmt/c5t3d0BEST is assigned to the drive, if not, use the file assigned to the drive

If it is assigned to the correct tape device, then try removing the device files with rmsf -H and reinstalling them with insf -H

[lin.chen]

I have test with "tar",it seems OK.
but fbackup never succeeded!
I wonder whether HP "fbackup" can support such kind of tape drive?
thanks man!

[Patrick Wallek]

It is possible, in fact quite probable, that you need a patch for fbackup to enable it to talk to an Ultrium device.

Since you did not specify your HP-UX version, here are options for HP-UX 11.0 and 11.11:

HP-UX 11.00 - PHCO_33201
http://www1.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_33201&sel={hpux:11.00,}&BC=main|search|

HP-UX 11.11 - PHCO_28998
http://www1.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_28998&sel={hpux:11.11,}&BC=main|search|

[DCE]

If tar worked to the same device file, then fbackup should work as well.

The man page for fbackup staes it will backup to any raw magnetic tape drive.

Did you recently replace the drive? If so I would recommend recreating the drivers

[Marcel Burggraeve]

fbackup and frecover are really picky about the microcode in the tapeunit like someone else stated as well.
If they see a microcode which is unknown they simply won't work.
Seen this at a customer once when a repair company replaced internal parts of a DLT8000 after which it ended up with a quantum microcode if memory serves me right.
After logging a call and some investigation HP told that customer it was the microcode causing the problems.
On that device tar and such still worked but fbackup refused to work.

I wouldn't know what brands and types have valid microcode though.
I have experience with IBM LTO units working perfectly with fbackup on a HP9000.