/dev/rmt/0m not a valid device file for backup

[Sean Donovan]

Recently I connected a Ceratance LTO 2 tape drive to my HP-UX 11.11 system in order to create a ignite tape.Ignite ran error free and a subsequent test restore ran successfully.
However when I run #fbackup -f \dev\rmt\0m -u0g graph -I index.tst I recieve the following message "dev/rmt/0m not a valid device file for backup".An ioscan confirms the device exists.Any help would be sincerely appriciated.

Thanks-Sean

[AwadheshPandey]

http://www.webservertalk.com/message392429.html

[Jollyjet]

u can try this

fbackup -f `hostname`:/dev/rmt/0m ...
frecover -x -f `hostname`:/dev/rmt/0m ...

[Sean Donovan]

Thanks for your response.When I run # fbackup -f 'hostname':/dev/rmt/0m -i /home the results are the same.I have listed the output below.Are there any other suggestions?

fbackup(1004): session begins on Tue Oct 23 19:39:46 2007
fbackup(3301): could not open output file titan1:/dev/rmt/0m
fbackup(3019): would you like to enter a new output file?

[Bill Hassell]

fbackup is quite different than dump backup tools like tar and cpio. They do not interact with tape drives while fbackup relies on several tape functions for high performance. You'll need the latest patches:

PHCO_28998 or PHCO_36630 fbackup cumulative
PHKL_34552 SCSI tape driver cumulative
PHKL_27830 or PHKL_34805 JFS patch

Even then, Certance tape drives may present a problem for fbackup. Be sure to check with Quantum (who aquired Certance in 2005) for either firmware updates or possible feature switch settings in the drive for HP-UX support.

[whiteknight]

Sean,

make sure you have this patch installed and try again

PHKL_34552 11.11 SCSI Tape (stape) cumulative
or
PHKL_31500 11.23 Sept04 base patch

WK

[jmreyes]

hi sean,

make sure that ur tape is working before u perfomed the fbackup.

and other thing check below may be it can help.....

'fbackup' behaves slightly different when using remote devices. You
can specify a device on the remote system in the form machine:device.
'fbackup' creates a server process from /usr/sbin/rmt on the remote
system to access the tape device. If /usr/sbin/rmt does not exist on the
remote system, fbackup creates a server process from /etc/rmt on the
remote system to access the tape device. In order for 'fbackup' to
function properly, local systemA must be able to remsh or rlogin to
remote systemB without being prompted for a password.

Note: See the 'fbackup' man page.

Verify these conditions for the local and remote systems:

1. Verify that the name resolution on the local and remote systems
are identical:

Local systemA:
#nslookup
Using /etc/hosts on: machine

> hostname
Using /etc/hosts on: machine

Name: hostname.domain.com <-- name to use for rpc,rhosts,host.equiv
Address: 115.56.23.14
Aliases: machine,aliases <-- don't use aliases

regards,

joey