fbackup delay long time

[Isaac_4]

Hi: I have a problem when use Fbackup command to made a full backup system, following is the sintax that use for them :
(with fbackup the process, stay in spleep mode and delay arrow 14 hours, when in the past delay arround 2 hours, and we have the same quatity of data. We change the DDS3 to discart a hardware problem. We have other Drive but is the same error with it)


fbackup -f /dev/rmt/0m -i / -I /tmp/backuplist.txt

I use other utilites for backup like tar, cpio and ignite and all of work fine and fast.

Some one have a Idea ?

Thank a lot

[IT_2007]

Do you have any NFS mount points?
Check syslog for any errors.

run fbackup to backup like some directory size of 4GB and see how much time it takes to complete?

Also check size of fbackup binary file.

-r-xr-xr-x 1 bin bin 77824 Apr 17 2003 /usr/sbin/fbackup

[James R. Ferguson]

Hi Isaac:

Two thing immediately come to mind.

First, 'fbackup' is designed to work while files are inuse. 'fbackup' attempts to insure a good copy of a file is placed on tape by comparing the timestamp of the file at the end of the copy to the timestamp of the file seen at the beginning of the transfer. If these do not match, 'fbackup' marks the file as "bad" and retries the copy. The retry ('maxretries') default is five (5) and can be defined in the 'config' file associated with 'fbackup'. Thus, if you have files that are changing as you attempt to back them up, you will spend considerable time retrying their copy whether or not that copy is ultimately successful.

Second, be sure to specify your own configuration file for 'fbackup'. The default values that you will otherwise obtain are out-dated and will generally give very poor performance during backup and recovery. Build a configuration file that looks like:

blocksperrecord 4096
records 64
checkpointfreq 4096
readerprocesses 6
maxretries 5
retrylimit 5000000
maxvoluses 200
filesperfsm 2000

The manpages for 'fbackup(1M)' document the default settings which is what you will get in the *absence* of an explicily defined set.

These parameters are recorded onto the actual backup tape and are thus used for a 'frecover' session too.

Checkpoint records allow the salvage of a backup when a bad tape spot is detected, since the records contain information about the file being backed up. The 'filesperfsm' parameter controls the frequency with which Fast Search Marks (FSM) are written. Both checkpoint and FSM records affect performance. FSMs take a tape drive out of streaming mode thereby adding to backup time. Conversely, however, FSMs improve the time it take to recover a file from tape.

In general, if your backup consists of a high proportion of small files, increase the value for 'filesperfsm'. If your backup consists of a high proportion of large files, then decrease the 'filesperfsm' value.

Regards!

...JRF...

[Bill Hassell]

Are you backing up a *large* number of files *and* you have almost no RAM installed (ie, less than 1000 megs)? Then the answer id=s that this is perfectly normal. fbackup does not simply copy files to tape like tar. Instead, it starts by finding every file you asked for and storing information about the file into shared memory. For a very small system, it will take between 60 and 100 megs to hold all these file and directory names. For tens of thousands of files, you'll need as much as 200 to 400 megs of shared memory. Once the files have been found, a complete index is created on the tape by reading this shared memory area, then at least 4 and up to 6 copies of the file-reader program are started to keep the tape busy.

If you do not have enough RAM, the HP-UX will keep running by using swap space. While this is a very nice feature (to run a lot more memory than actually installed), your system will be massively paging (swapping) so performance will be awful. Add a couple of gigabytes of RAM and try again.