most of my incremental fbackups report Exit Code = 2

[Basheer_2]

HP-UX 10.20
I do my full backup on sunday, I get Exit Code = 0 (Success).

But almost all of my incremental (daily backups) show that incremental backup failed with Exit Code = 2 (var/sam/log/br_log)
(I start backup job 3 AM in night)

Which means backup with errors.

Is it possible to know what kind of errors.

frecover -V /tmp/junk Doesn't give much info.
Where else I can get some info on what exactly these errors are. ( I do fbackup from SAM)

Thanks

[Steven E. Protter]

Files might be locked,

Files might have been deleted in the time interval between the list being made and the actual backup happening.

You may be trying to back up open oracle databases. This won't work unless the database is shut down at the time of backup.

SEP

[Darren Prior]

Hi,

br_backup (the script called by SAM) does hide the error numbers that fbackup provides - if you have set br_backup so that it emails someone the output then this could provide some further clues as to where the problem is.

Check the crontab entry to see whether it contains an email address to email out to. You could also compare the output from frecover with the -N option against the frecover -I output.

frecover -I will list the index of files that were intended to be backed up, whereas the frecover using -N (check the man page for other options) will perform a full recovery but without actually writing any files to disk, and this will show you which files actually have been backed up.

An alternative would be to write your own backup script, specifically for your needs, that captures the errors so that you can check through them.

regards,

Darren.

[Paula J Frazer-Campbell]

Hi

Exclude the tmp dirs from your full backup as these files can exist when fbackup checks to see what to backup and because they are temp they get removed by the system and fbackup screams exit code 2 because the file was not there when it required it, which could be hours later.

Paula

[James R. Ferguson]

Hi:

Files that are present at the start of 'fbackup' but removed prior to the time when they are actually copied, generate 'unable to stat' warnings, not errors.

Files that are actively changing or locked are retried 'maxretries' times as defined in the 'config' file (the default retry is five (5) in the absence of the file). Successful retries are warnings only.

Errors (rc=2) are generally due to bad tapes; tapes which are write-protected; and requests for continuation volumes when the task has been cron-initiated without provision via a 'chgvol' script (see the 'fbackup' man pages).

Regards!

...JRF...

[Paula J Frazer-Campbell]

James

I stand corrected
:-(

Some new every day - I hope

Paula