fbackup Problem

[Ashwin_4]

Hi Masters,
I'm getting the following error while taking fbackup on DDS-3 drive with HP-UX 11.0,

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?

# mt -f /dev/rmt/0m stat
Drive: HP C1537A
Format:
Status: [0]
File: 0
Block: 0

[Ashwin_4]

ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Descripti
on
================================================================================
===
tape 0 0/0/2/1.0.0 stape CLAIMED DEVICE HP C
1537A
/dev/rmt/0m
/dev/rmt/0mb
/dev/rmt/0mn
/dev/rmt/0mnb
/dev/rmt/c3t0d0BEST
/dev/rmt/c3t0d0BESTb
/dev/rmt/c3t0d0BESTn
/dev/rmt/c3t0d0BESTnb
/dev/rmt/c3t0d0DDS
/dev/rmt/c3t0d0DDSb
/dev/rmt/c3t0d0DDSn
/dev/rmt/c3t0d0DDSnb

[saju_2]

Hi ashwin

Pls gothrough the below thread..

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=96301

[morganelan]

Hi,
Please see this link:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=733178

[Joseph Loo]

hi,

have u patch stape recently? or rather what is the patch level for stape?

the recommended patch is PHKL_27303 but depend on (of course) base patch PHKL_18543

regards.

[Cem Tugrul]

Hi Ashwin,

how about these steps?

1-Be sure about the connections,cables,scsi ids aout your tape drive

2-rm /dev/rmt/*

3- insf -e

4- ioscan

5- try fbackup again

Good Luck,

[Ashwin_4]

I have gone through above threads but vain..

Do I need to apply some patches. The drive was running fine few days back.

[Joseph Loo]

hi,

run swlist to check the current stape patch level:

# swlist -l patch|grep stape

but really, i believe u may have to apply that recommended patch.

u may also want to do something about assigning points to others:

http://forums1.itrc.hp.com/service/forums/pageList.do?userId=CA1031169&listType=unassigned&forumId=1

regards.

[john korterman]

Hi,

I cannot remember if you can make a successful status command if the tape is not correct, but just to make sure: has the tape been successfully used before?
Is the length of the tape correct?


regards,
John K.

[Ashwin_4]

Hi Loo,

# PHKL_22161 1.0 SCSI Tape (stape) cumulat
ive
# PHKL_22287 1.0 SCSI Tape (stape) cumulat
ive
# PHKL_27303 1.0 SCSI Tape (stape) cumulat
ive

[melvyn burnard]

This looks like there is a problem with the media.
Have you tried other tapes?
also check the write protect tab. And maybe give the tape a clean with the cleaning tape.

You could also test it by using tar, cpio or dd.

[Cem Tugrul]

i am agree with Melvyn...

[Gavin Clarke]

I like the media suggestion. It seems like something that has changed in the last few days.

I almost suggested it myself and then didn't, more fool me.

Could we see the exact fbackup command and an ll of /dev/rmt as well just in case that sheds any light please?

[Ashwin_4]

Hi,
I have cleaned the drive and used the new media still the problem persists.

[melvyn burnard]

and does tar or cpio or dd also fail? or do they work?
If they also fail, I suspect it is time to get a hardware call logged.

[Gavin Clarke]

Can you post the command you are running and an ll of /dev/rmt please? It is just to satisfy my curiosity really, I feel like there is a piece of the puzzle missing.

[Ashwin_4]

/usr/sbin/fbackup -0f /dev/rmt/0
m -g /sysbckup/bgraph1

crw-rw-rw- 2 bin bin 205 0x030000 Aug 10 18:14 /dev/rmt/0m

[Gavin Clarke]

Does using /dev/rmt/c3t0d0BEST produce the same result?

Are there any fbackup processes already running?

We had a problem before where two backups were running quite close together and one caught the other up.

I suspect Melvyn has probably already got this nailed. I'm just seeing if there's any other info that might help me understand what is happening.