Back_up problems

[Carter Jay]

Hello,

I've got a problem when I launch an automated backup with sam...
Here is the log file of View History log:
Full backup started on manon : Mon Aug 19 23:00:00 WETDST 2002 (Scheduled Backup)
{ fbackup -0 -u -g /etc/sam/br/graphRCAa09149 -I /var/sam/log/br_index.full -c /etc/sam/br/fbackup_config -d /var/adm/fbackupfile
s/dates -f /dev/rmt/0mn } 2>&1
Full backup failed on manon : Tue Aug 20 00:02:25 WETDST 2002 .
Exit code = 4

But when I look in View Full Backup log, I've got:
1024 0 /
298 0 /.ICEauthority
154 0 /.TTauthority
147 0 /.Xauthority
1024 0 /.dt
96 0 /.dt/Desktop
96 0 /.dt/Trash
96 0 /.dt/appmanager
0 0 /.dt/errorlog
107 0 /.dt/errorlog.older
96 0 /.dt/help
Which confirms it worked, and that's the same with Get List of files on device.
The bck mail is:
br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1004): session begins on Mon Aug 19 23:00:00 2002
fbackup(3203): volume 1 has been used 1 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/0mn
fbackup(1102): WARNING: unable to stat file /var/spool/sockets/pwgr/client12270
fbackup(1102): WARNING: unable to stat file /var/spool/sockets/pwgr/client12327
fbackup(3005): WARNING: file number 222724 was NOT backed up
fbackup(3005): WARNING: file number 222726 was NOT backed up
fbackup(1030): warnings encountered during backup
fbackup(3055): total file blocks read for backup: 41548571
fbackup(3056): total blocks written to output file /dev/rmt/0mn: 42482056

What could be this problem?
The first file on the tape is a dd file, could it be the problem?
How can I remove this file? (mt commands)

Thanks in advance

Best Regards

Jerome

[Stefan Farrelly]

The WARNING messages in your backup log are nothing to worry about - they are simply temporary files/socket files which were in use at the time of the backup so werent backed up. This is nothing to worry about.

If you use frecover -I to read the backup tape back you will see its backed up aok.

[Ceesjan van Hattum]

Just do not backup /var/spool/sockets:
fbackup ... -e /var/spool/sockets ...
That's all.

Regards,
Ceesjan

[john korterman]

Hi,

you should not use the non-rewinding device for fbackup.


regards,

John K.

[Steve Steel]

Hi

You have an exit code 4

exit code 4 could mean anything from encountering a blank tape
(where fbackup cannot read a header and warns that the tape may have been
used more often that voluses would indicate), to I/O errors that prevented
files from getting saved.

I suspect i/o errors .

Remember the fbackup makes and writes a backup log at the start of the tape and then does a backup.Thus there is no 100% guarantee that the content of the log is on the tape.

Check with frecover using -N


-N (no recovery) Prevent frecover from actually recovering
any files onto disk, but read the backup as if it was,
in fact, recovering the data from the backup, producing
the same output that it would on a normal recovery.
This option is useful for verifying backup media
contents in terms of validity (block checksum errors
are reported), and contents (a listing of files can be
produced by using the -N and -v options together).
Note that the listing of files produced with the -N and
-v options requires the reading of the entire backup,
but is therefore a more accurate reflection of the
backup's contents than the index stored at the
beginning of the backup (which was created at the start
of the backup session, and is not changed during the
course of the backup).


Steve Steel

[Sebastian Galeski_1]

Hi
my advice is to run backup from command line, i always do it this way:
for hpux 11.11
#nohup fbackup -f /dev/rmt/0m -i / -v 2> /tmp/backup.log

for 11.00
#nohup fbackup -f /dev/rmt/0m -i / -v > /tmp/backup.log

regards seba

[Frank Slootweg]

Adding to the other responses:

As has been mentioned, "Exit code = 4" is a *warning*, not an error, *but* it is a *new* exit code (RETURN VALUE) from fbackup, so if you have a new(er) fbackup and an old(er) SAM, then SAM will think it is an error because it does not 'know' exit code 4.

So make sure that you are up-to-date on fbackup *and* SAM patches.