1832968 Members
2339 Online
110048 Solutions
New Discussion

Re: fbackup(3044)

 
Diane Hager
New Member

fbackup(3044)

Our daily backup took the following error during last nights run:
=====
fbackup(3044): ioctl error, can't query outfile at media record 12628
=====
Could someone assist us with this ?
4 REPLIES 4
CHRIS_ANORUO
Honored Contributor

Re: fbackup(3044)

The problem is that someone was working on related files, this caused the file to be lock during backup.
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
Luis Lopez_1
Occasional Contributor

Re: fbackup(3044)

My Version :
HP-UX B.10.01 A 9000/801
************************
i.e. :
Session 1
=======
# fuser ?u clie*
...
clien00121.dat:
clien00121.idx:
clien00282.dat: 16651o(apolo)  FILE IN USE
clien00282.idx: 16651o(apolo)  FILE IN USE
...
Session 2
=======
# vi file_graph :
i ./clien00121.dat
i ./clien00121.idx
i ./clien00282.dat
i ./clien00282.idx

Command fbackup with options : -0 ( zero )

# fbackup ?0 -v -u -g./file_graph -f /dev/rmt/0m
fbackup(1421): no history is available for graph file ./file_graph (below level 0)
fbackup(1004): session begins on Thu May 11 17:21:26 2000
fbackup(3203): volume 1 has been used 7 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/0m
1: .
2: ./clien00121.dat
3: ./clien00121.idx
4: ./clien00282.dat
5: ./clien00282.idx
fbackup(1005): run time: 35 seconds
#

Verify this fbackup :
*********************
# mkdir tmp2; cp file_graph tmp2; cd tmp2
# frecover -xvo -g./file_graph
-rw-rw-rw- apolo informix ./clien00121.dat
-rw-rw-rw- apolo informix ./clien00121.idx
-rw-rw-rw- apolo informix ./clien00282.dat
-rw-rw-rw- apolo informix ./clien00282.idx
FILE RECOVER SUCCESSFULL ? O.K. Sizes ?!
Fernando Pena
Vince Arends
Frequent Advisor

Re: fbackup(3044)

I had the same problem a few weeks ago. I called HP Hardware Support. They said either firmware in the tape drive somehow got bad or the drive itself was going out. They replaced the drive unit (it was still under warranty) and the problem has not happened since.
Evan Day
Occasional Advisor

Re: fbackup(3044)

This problem is most likely either a failing tape drive (as stated above), a dirty tape drive (run cleaning tape through a couple times), or a bad tape. I've seen similar errors in all three cases. If cleaning and using a new (fresh out of the wrapper) tape doesn't clear the error, call your hardware support contractor to replace the drive.