fbackup running hours

[Ulrich Tehrani]

Hi,

has anybody an idea why my backup (running fbackup) normally takes just 20 minutes and in scarce cases takes several hours. Maybe there are files in use but that couldn't be the reason or?

Thanks in advance
Uli

[Michael Tully]

no, certainly this would not be the reason. 'fbackup' takes a snapshot of files prior to starting, then if a file is busy, reports this. It does not wait. I would say, that you either have a tape problem or a drive problem. Clean the drive and try some new tapes.

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome."

[twang]

yes, i have same experience before, to find out the cause, you may:
-. clean the tape drive and rerun the command

-. use tar or cpio to do the backup and see the result.

-. see dmesg or syslog.log for any hardware alert message.

[Steve Steel]

Hi

Have a look at making a config file for fbackup and set maxretries on 2.

Then see if the problem still exists.

fbackup makes a snapshot but if a program opens while the fbackup is busy it will retry each open file 5 times by default and that can take time.

try the -v runtime option.

-v Run in verbose mode. Generates status messages that
are otherwise not seen.

Also try the tape as suggested


Steve Steel