fbackup log

[Ionut Grigorescu_2]

Hi,

I have performed a full backup with:
#fbackup -0i / -v -f /dev/rmt/c0t0d0BEST > /tmp/fbackup.log 2>&1
at the end of the file I got the line:
fbackup(1030): warnings encountered during backup
I have searched the file with the pattern "warning" (the file is about 30 MB large) - there are only filenames like xxxxwarningxxx but no warning from the fbackup - is the backup OK?

ionut

[Con O'Kelly]

Hi

Yes the backup is most likely OK.
Often warning messages are written when files that existed when the backup commenced are removed during the backup (eg files in /tmp /var/tmp etc).

If you post the exact warning, then I'm sure someone will confirm its OK.

Cheers
Con

[Tim Adamson_1]

Hi,

can you post the warnings ??

Cheers

[Rajeev Shukla]

Ya thats ok, you might get warning for say socket files etc..If you dont see anyother warnings other than that the backup is ok.
Dont worry

Rajeev

[malay boy]

well sometime our weekly backup hit warning alert.Normally what I do is to do a listing or just revover one file to check whether the backup is fine.Just run below command to get the listing of the backup :

frecover -x -I /tmp/index -f

regards
mB

[Michael Tully]

Hi,

Warnings in 'fbackup' are quite normal. Most of the time these warnings are from files that are there at the time the snapshot of the backup starts, but when the backup gets to that file it has been removed.

HTH
Michael

[Ionut Grigorescu_2]

OK,

the last lines in the fbackup log:

fbackup (1005): run time: 4821 seconds
fbackup(1030): warnings encountered during backup
fbackup( 3055): total file blocks read for backup: 14493502
fbackup(3056): total blocks written to output file /dev/rmt/c0t0d0BEST: 15331209
that's all
I got MC/SG on the server (HPUX11.00) but I stopped the MC/SG before backup, change the vg's to non-clustering, activate and and remount the FS manually.
If a file is modified during the backup I should receive a warning and I should see the warning in the log file.

cheers, ionu

[BFA6 · Accepted solution]

Hi,

check for WARNING. It could be somethin as simple as a new tape, which means fbackup cannot read a header (as there wouldn't be one)

Regards,

Hilary

[Massimo Bianchi]

Hi,
maybe the information we are looking for are in the beginning of the file.

Some warning are for the tape being used for NN time or similar...

Massimo

[Chris Wilshaw]

A full list of errors from fbackup can be obtained using;

dumpmsg /usr/lib/nls/C/fbackup.cat

if you just want to see the possible warning messages, use

dumpmsg /usr/lib/nls/C/fbackup.cat | grep -i warning.

This will also provide you with the fbackup error codes (the values in brackets) which can also be used to check the status of your backup.

[Ionut Grigorescu_2]

Hilary: I have all the time searched for warning not WARNING - that was the clue. The warnings were something like :
cannot stat file /tmp/aa...etc.
I have readed on the forum what's the cause - nothing to worry about.
Thank you all, case closed.