backup warnings

[Ahmed M. AlShafiy]

we are backing up our database using SAM auto-backup but i get this message that i don't get it befor:

Full backup completed with warnings on nasjet : Sat Feb 4 20:30:31 WAT 2006 .
For more information see the logfiles /var/sam/log/br_index.full and /var/sam/log/br_log.
Output from fbackup:

br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1004): session begins on Sat Feb 4 19:40:01 2006
fbackup(3205): WARNING: unable to read a volume header
fbackup(3024): writing volume 1 to the output file /dev/rmt/0m
fbackup(3055): total file blocks read for backup: 54311667
fbackup(3056): total blocks written to output file /dev/rmt/0m: 54410036
fbackup(1030): warnings encountered during backup

there is a backup warning in last line what is that ?

[Arunvijai_4]

Hi Ahmed,

Did you check /var/sam/log/br_index.full and /var/sam/log/br_log ? I believe, as fbackup says, fbackup(3205): WARNING: unable to read a volume header.

-Arun

[Ahmed M. AlShafiy]

so, what can i do with this tow warning 3205 and 1030?

i check the file br_log and i find this:

Full backup started on nasjet : Sat Feb 4 19:40:00 WAT 2006 (Scheduled Backup)
{ fbackup -0 -u -g /var/sam/graphPCAa27906 -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 nasjet : Sat Feb 4 20:30:32 WAT 2006 .
Exit code = 4


and the br_index.full there is no error on it but the file size 1.39 MB.

[Robert-Jan Goossens_1 · Accepted solution]

Ahmed,

Did you use a new tape (on a new tape there is no volume header) ?

Problem: Lack of a volume header (this will most likely occur with a new tape)
Solution: Fbackup will scan new media for a volume header before it begins
an archive. If the header is not present fbackup will create the header and
complete its execution but return code 4. This is only to let you know that this
condition occurred.

Regards,
Robert-Jan

[Steven E. Protter]

Shalom Ahmed,

Your tape is getting old.

Best bet is to get a fresh one, clean the tape heads with a cleaner tape and themessage will probably go away.

The backup is probably okay, but eventually the tape will become useless.

You can not use tapes forwever.

SEP

[akdkumar]

Hi Ahmed,

Since it is a warning message your backup is likely to be okay. I suggest yo test restore operation to confirm. Probably the tape contains a nonstandard previous backup.

Regards

Dinesh

[Luk Vandenbussche]

Hi,

This is your warning messages

fbackup(3205): WARNING: unable to read a volume header


You used a tape the first time with fbackup, so there was no volume header on the tape.

Your backup is OK, next time you use this tape you will not see this error

[Ahmed M. AlShafiy]

and how about 1030 ?

[Robert-Jan Goossens_1]

fbackup(3205): WARNING: unable to read a volume header ---> new tape or a tape with NO fbackup header (cpio,tar etc)

fbackup(1030): warnings encountered during backup

Correct the fbackup repported a warning (3205).

[Nguyen Anh Tien]

In fact, the "4" is the exit code or return value documented in the
man page:

RETURN VALUE
fbackup returns one of the following values:
...
4 if any warning conditions are encountered.

[shridhar_1]

hi

ur backup is ok

check with

frecover -xvf /dev/rmt/0m -i /urdir -N

-------------------------------------------
-N -- will not restore but only shows
what will be restored try a small
directory with -i option

refer man frecover

shri

[Ahmed M. AlShafiy]

thanks all of you ...