Using fbackup to a Seagate Viper LTO1 on a J5600

[Chris Knowling]

Hi all, this is my first post on ITRC!

I know there's a few posts on the topic of fbackup/frestore and LTO drives. I've read all I can find and none of the suggestions I've researched and implemented have given me success.

The drive is in good shape, external and attached to the onboard LVD bus. 'ioscan' gives its details fine, 'mt' can control it and 'tar' can backup to it successfully also.

Background info is in the attached text file.

When fbackup is invoked from SAM i get the following output:
Starting interactive backup...
br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1421): no history is available for graph file /var/sam/graphNCAa24146 (below level 0)
fbackup(1004): session begins on Tue Apr 3 16:33:29 2007
fbackup(3038): output file /dev/rmt/1mb is not a valid device file for backup
fbackup(3019): would you like to enter a new output file?

Any assistance would be appreciated.
-Chris

[Steve Lewis]

I use /dev/rmt/1m, not /dev/rmt/1mb

I assume that fbackup supports Berkeley devices, but maybe it doesn't.

See if that device file exists:
ls -l /dev/rmt/1mb

Then check that you have the required patch for fbackup to support an LTO 1. I think it is PHCO_28998 for HP-UX 11iv1. Which version of HP-UX are you using?

[Bill Hassell]

fbackup must always be patched to the highest level possible to support new tape drives. Unlike tar or cpio, fbackup needs specific knowledge about the tape drive. Also make sure you are using the recommended config file. Otherwise, backup performance will be awful.

[Chris Knowling]

Thanks for your comments guys. I am fully patched, if you read the attachment I included listing of relevant patches.

I guess I'll leave this as a hopeless case and stick to using tar...

[Bill Hassell]

For fbackup:
11.00 PHCO_29197
11.11 PHCO_28998
11.23 PHCO_31622

If one of these patches is installed, then the Seagate LTO is apparently not supported. Try to trade for an HP LTO.

[Chris Knowling]

Thanks once again all, I'm going to close this thread as it seems the drive simply isn't supported.

[Chris Knowling]

closed.