1846437 Members
2963 Online
110256 Solutions
New Discussion

fbackups problem.

 
Sreedhar B N
Occasional Contributor

fbackups problem.

Hi gurus,

This is the system configuration.
L1000/exabyte Tape drive
OS: HPUX 11.00

Problem: When do backup through command line or through SAM to the tape drive I get the following message.

fbackup(1005): run time: 649 seconds
fbackup(3055): total file blocks read for backup: 3769688
fbackup(3056): total blocks written to output file /dev/rmt/0m: 3859396
fbackup(1030): warnings encountered during backup

If any one is facing the same problem pls let me know the fix.
Nothing is Free in this world.
5 REPLIES 5
Edward Sedgemore
Trusted Contributor

Re: fbackups problem.


Whats the problem ? looks like your backup worked fine to me. The message about runtime being only a relatively small number of seconds is not a problem.
As for the warnings, you need to look at the fbackup log for more detail on which files were in use at the time of the backup hence they werent backed up.
Pedro Sousa
Honored Contributor

Re: fbackups problem.

Hi!
It seems it worked ok! The message "warnings encountered during backup" can be related to the fact that some files were in use when fbackup was running!
Per example, if you have any DB running, you should stop it before!
Vincenzo Restuccia
Honored Contributor

Re: fbackups problem.

Check in /var/sam/log for errors.
Paula J Frazer-Campbell
Honored Contributor

Re: fbackups problem.

Hi

This is a normal warning from fbackup and usually means that files were in use (locked) during the backup run.

Fbackup will make 5 attempts to backup an open file and then if unsuccessful, write an error to log and continue on.

For Fbacbup to be most reliable your machine needs to be in single user mode, see man fbackup

Paula
If you can spell SysAdmin then you is one - anon
James R. Ferguson
Acclaimed Contributor

Re: fbackups problem.

Hi:

Warnings (return code=4) can be due to inuse files which may or may not be backed up. As Paula notes, you have the option of in the fbackup configuration file. The default value if you don't specify it is <5>. If the file is backed up on the second try, you still get the warning.

Another cause of the warning (returncode=4) if when fbackup uses a tape that wasn't last used by fbackup. This could be a virgin tape or simply one to which a 'tar' was last done. 'fbackup' records a header on the tape it uses, including a running count of the number of times the tape has been used.

...JRF...