backup using fbackup command

[badrul]

i using this syntax .....
#fbackup -v -i /ex2/liveBackup/Tape -c /etc/sam/br/fbackup_config -f /dev/rmt/1m

the data about 95GB to backup
the time 8 hours still not finished.

it's i a true time or maybe have a problem

while the fbackup start the message warning is'unable to read volume header'

[Sundar_7]

8 hours for 95GB..not too bad..but also depends on the kind of tape drive you are writing to.

Post the following info

1) contents of /etc/sam/br/fbackup_config

2) Kind of tape drive you are writing to

3) whether hardware compression is enabled in the tape drive or not ?

[Bill Hassell]

Very important pieces of information are missing:

- what is the model of the tape drive?

- what model computer is being used?

- What other programs are running on the system?

The reason that these are crucial to answering your question is that a very new Ultrium drive, it may be way too fast for your computer. With new tape drives, they will run VERY slow if the computer cannot deliver data fast enough.

[twang]

- fbackup shows the message warning 'unable to read volume header' as using a new tape.
- to store a particular directory:
# fbackup -f /dev/rmt/1m -i /ex2/liveBackup/Tape

- to see what's actually on the tape without restoring then:
# frecover -Nrosv -f /dev/rmt/1m > your_filename 2>&1

[Bill Hassell]

The error message "Uanble to read header..."

fbackup knows it's own format and expects to see it on existing tapes. If the header is not found (new tape, previously used with tar, cpio, etc), you'll getr the warning. It's not a problem, just fbackup identifying the tape before using it. fbackup will never overwrite it's own backup using this method. tar, cpio, etc will overwrite an existing first volume of a backup when a second volume is required, but fbackup sees the first volume header and refuses to use it as a second tape for the backup.