fbackup(1030): warnings encountered during backup: 4

[Sanjiv Sharma_1]

Hi All,

I have a J6000/HP-UX 10.20 with DDS3 tape drive.

It has been observed that when I run the fbackup with the following command:
# fbackup -f /dev/rmt/0m -u0g graph01 -I index.full

It takes the backup but gives a warming message at the end and comes to the unix prompt:
fbackup(1030): warnings encountered during backup: 4

This message was not coming till yesterday.
Even the sam fbackup gives the same message.

What could be reason?

Thanks,
Raje.

[Patrick Wallek]

The first thing you need to do is check the fbackup log file, I can't remember the location at the moment, and see what the exact warnings are. Without seeing the messages, we can't really tell you what the case is.

[Animesh Chakraborty]

Hi Raje,
Warnings means some files were open or being used at the time of fbackup.
Look log file for details
it may be in /var/sam/log/br_log

[Sanjiv Sharma_1]

Hi PAtrick/Animish,

# fbackup -f /dev/rmt/0m -u0g graph01 -I index.full
fbackup(1004): session begins on Fri Sep 27 11:38:21 2002
fbackup(1517): /net not backed up - 'n' option (NFS) not specified
fbackup(3203): volume 1 has been used 1 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/0m
fbackup(3007): WARNING: File number 18355 (/opt/ns-enterprise3/https-tiger/logs/
access)
was active during attempt number 1
fbackup(1301): resuming at file 18355
fbackup(1030): warnings encountered during backup: 4
#


Message in /var/sam/log/br_log

Full backup started on ijmsls01 : Fri Sep 27 10:57:42 SST 2002 (Scheduled Backup
)
{ fbackup -0 -u -v -g /etc/sam/br/graphFCAa27828 -I /var/sam/log/br_index.full
-c /etc/sam/br/fbackup_config -d /var/adm/fbackupfiles/dates -f /dev/rmt/0m } 2
>&1
Full backup completed with warnings on ijmsls01 : Fri Sep 27 11:21:23 SST 2002 .
Exit code = 4

Thanks,
Raje.

[Animesh Chakraborty]

Raje,
Don't worry it is just a warning not error.
I think your fbackup still usable.
If u get exit status 2 then it is problem.

[Elif Gius]

Hi Raje,

it's not a serious problem.
With some backups we have the same error message, but it is already a warning.

Our logfile looks like this:
...
fbackup(1102): WARNING: unable to stat file /var/spool/sockets/pwgr/client8901
fbackup(1102): WARNING: unable to stat file /var/spool/sockets/pwgr/client9291
fbackup(1102): WARNING: unable to stat file /var/spool/sockets/pwgr/client9585
fbackup(1102): WARNING: unable to stat file /var/spool/sockets/pwgr/client9587
fbackup(1102): WARNING: unable to stat file /var/spool/sockets/pwgr/client9599
fbackup(3005): WARNING: file number 51555 was NOT backed up
fbackup(3005): WARNING: file number 51556 was NOT backed up
fbackup(3005): WARNING: file number 51559 was NOT backed up
fbackup(3005): WARNING: file number 51560 was NOT backed up
fbackup(3005): WARNING: file number 51562 was NOT backed up
...
RETURNCODE 4

But as you can see, the other backuped files are not invoked.

[Darren Prior]

Hi Raje,

The warning 3007 is just an indication that a file was active when fbackup was trying to write it to tape. In an ideal world backups would only be run when the system was in single user mode and you wouldn't have any active files. The 1301 message suggests that on the next attempt to backup the file it wasn't active.

Potential workarounds:

* stop all your applications when you wish to run a backup

* change the graph file to exclude that dir

* accept that you may get an warning, and remember to check the fbackup logs after each backup.

regards,

Darren.

[john korterman]

Hi Raje,
before fbackup starts writing a file to tape it checks the timestamp of the file. The timestamp is checked later - for a big file, possibly both during and after writing data to tape. If the timestamp changes, fbackup writes a "BAD" mark for that file on the tape. Then a warning like the one you got is issued. Fbackup then retries until either a copy with an unchanged timestamp is achieved, or the no. of maxretries has been reached (maxretries as specified in your "graph01" file).
In your session fbackup makes attempt no. 2 - (resumes with the file of same session number, 18355) after the warning. As there is no later warning you may conclude that attempt no. 2 worked.
However, warnings should be taken seriously: if, for instance, the number of retries has been exhausted and no successful copy has been made, fbackup will still only issue a warning - and you can restore nothing from BAD marked files.

Regards,
John K.