fbackup shows 0 bytes written, but there are no errors

[Dave Chamberlin]

Greetings

Running fbackup (hp-ux 11.11), the session runs for a while, and completes but indicates 0 bytes written to output: The indexfile is created and shows the files it should. Is it really working?

Saturn# fbackup -f jupiter:/dev/rmt/1m -g graph_test -I indextest082812

fbackup(1601): could not access -i/-e file /s03

fbackup(1601): could not access -i/-e file /u20

fbackup(1601): could not access -i/-e file /u21

fbackup(1601): could not access -i/-e file /u22

fbackup(1601): could not access -i/-e file /u32

fbackup(1601): could not access -i/-e file /u33

fbackup(1601): could not access -i/-e file /u34

fbackup(1601): could not access -i/-e file /v1

fbackup(1601): could not access -i/-e file /v2

fbackup(1601): could not access -i/-e file /v3

fbackup(1601): could not access -i/-e file /iuxcdrom0

fbackup(1004): session begins on Tue Aug 28 15:57:44 2012

fbackup(3309): WARNING: unable to read a volume header

fbackup(3024): writing volume 1 to the output file jupiter:/dev/rmt/1m

fbackup(3055): total file blocks read for backup: 391311

fbackup(3056): total blocks written to output file jupiter:/dev/rmt/1m: 0

fbackup(1030): warnings encountered during backup

[pradeep m]

Perform the following: 

1. Check if the users can access (read/write access) those data files where warning occured. 

2. Make sure if the tape drive had enough free space. 

3. Check if there are any cron jobs or any other process accessing and modifying those data file during the time of backup. 
4.If so stop the cron jobs or any other process which is accessing those data file and perform the fbackup and check if it works without warnings this time.. 

Hope this helps..

[Dave Chamberlin]

I think the only warning was no volume header. Root ran the backup and has access to all. The tape is a clean LTO2 (200GB) and this test was 300M - so space was not an issue. Could be denied write by the remote host? The root user from the source is listed in the .rhosts file on the remote host.

[Dennis Handly]

>Could be denied write by the remote host?

I would think that would stop it with an error.

Have you tried using frecover to list what's on the tape?

[Bill Hassell]

>> fbackup -f jupiter:/dev/rmt/1m -g graph_test -I indextest082812

f>> backup(1601): could not access -i/-e file /s03

fbackup changes from a sophisticated backup tool to a primitive one when you specify a remote tape drive. fbackup loses information about the drive by using rmt on the remote system. As Dennis mentioned, use frecover -I /tmp/fbackup.idx -f /dev/rmt/1m

or

frecover -I - -f /dev/rmt/1m | more

to see the contents. Is the graph_test file in the correct format? That is:

i /s03

i /u20

i /u21

etc