fbackup through sam

[MD.IMTEYAZUL HASSAN]

i have utrium lto3 tape 400gb/800gb and having total ammount of data space is 262gb during backup through sam,but it was prompted for 2nd tape,can anybody help why this happen.

[Steven Schweda]

> [...] why this happen.

Perhaps you filled the first tape.


I see no description of the system where you
did this. Output from "uname -a" would be a
nice start.

> [...] backup through sam [...]

This does not seem to me to be a very
complete explanation of what you did.

> [...] utrium lto3 tape 400gb/800gb [...]

Does this tape drive have different density
and/or compression options? Which ones did
you specify?

Did you start with a blank tape?

[MD.IMTEYAZUL HASSAN]

$ uname -a
HP-UX Production1 B.11.23 U 9000/800 3021631172 unlimited-user license

$ /usr/sbin/ioscan -funCtape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/2/1/1.3.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/0m /dev/rmt/c5t3d0BEST
/dev/rmt/0mb /dev/rmt/c5t3d0BESTb
/dev/rmt/0mn /dev/rmt/c5t3d0BESTn
/dev/rmt/0mnb /dev/rmt/c5t3d0BESTnb
$


we have received message " fbackup(3310)enter (Y)when volume2 is ready on /dev/rmt/c5t3d0BEST, or (N) to discontinue."

Please suggest how to resolve this,so that i can take backup smoothly without any doubt

[OldSchool]

See this post:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1366891

and refer to Bill Hassell's remarks regarding a config file (or the lack thereof). You need to be able to keep the drive streaming and write fewer / bigger blocks.

Also, see my remarks about the impending demise of fbackup (it's being obsoleted).

Fbackup always rewinds the tape and starts at the begining, so you *should* be getting more that ~260MB on it. If you've got lots of bad spots, or lots of record gaps, that will reduce capacity.

What happens if you clean the drive and use a new (or known good) tape.

[Patrick Wallek]

Also make sure you are using an LTO3 TAPE in the LTO3 tape drive.

If you happen to be using an LTO2 (200 GB) or LTO1 (100 GB) tape, then that would explain your problem as well.