Operating System - HP-UX
1836438 Members
2574 Online
110100 Solutions
New Discussion

Clarification on fbackup warnings...

 
SOLVED
Go to solution
Phani_4
Frequent Advisor

Clarification on fbackup warnings...

Hi,

I am getting the following warning messages in my fbackup session. Please find the below o/p of fbackup.

fbackup(1004): session begins on Tue Jan 13 18:45:26 2004
fbackup(1517): /net not backed up - 'n' option (NFS) not specified
fbackup(3203): volume 1 has been used 35 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/0m
fbackup(3005): WARNING: file number 36544 was NOT backed up
fbackup(3005): WARNING: file number 36545 was NOT backed up
fbackup(3005): WARNING: file number 36546 was NOT backed up
fbackup(3005): WARNING: file number 36547 was NOT backed up
fbackup(3005): WARNING: file number 36548 was NOT backed up
fbackup(3005): WARNING: file number 36549 was NOT backed up
fbackup(3005): WARNING: file number 36550 was NOT backed up
fbackup(3005): WARNING: file number 36551 was NOT backed up
fbackup(3005): WARNING: file number 36552 was NOT backed up
fbackup(3005): WARNING: file number 36553 was NOT backed up
fbackup(3005): WARNING: file number 36554 was NOT backed up
fbackup(3005): WARNING: file number 36555 was NOT backed up
fbackup(3005): WARNING: file number 36556 was NOT backed up
fbackup(3005): WARNING: file number 36557 was NOT backed up
fbackup(3005): WARNING: file number 36558 was NOT backed up
fbackup(3005): WARNING: file number 36559 was NOT backed up
fbackup(3055): total file blocks read for backup: 3308471
fbackup(1030): warnings encountered during backup
fbackup(3056): total blocks written to output file /dev/rmt/0m: 3491891


Can somebody explains about these Warnings.Are these Warnings are really concerned ??

Thanks,
Regards,
Phani

7 REPLIES 7
Pete Randall
Outstanding Contributor

Re: Clarification on fbackup warnings...

Phani,

I would expect that these were temporary files that existed when the backup started but disappeared before they were able to be written to tape.


Pete

Pete
Hoefnix
Honored Contributor

Re: Clarification on fbackup warnings...

This happens when you start an fbackup that run's a long time. At start fbackup makes an index what it should backup. When some of these files are temporary files and they are delete during the fbackup-run it will report these errors.

Regards,

Peter
Phani_4
Frequent Advisor

Re: Clarification on fbackup warnings...

Hi Pete,

But from the below WARNING i observed that the number 36558 is may be an inode number of a file & could able to search those file in the system which are belongs to this inode number.

fbackup(3005): WARNING: file number 36558 was NOT backed up

Am i correct?

Phani
I.Delic
Super Advisor

Re: Clarification on fbackup warnings...

Hi Phani.

fbackup 3005
fbackup says that files 365544-36559 ara not backuped.
I don't now witch file the are . You have to check it youself.Maybe they are important and maybe not ( tmp file's)

Fbackup 1004 time your session started
Fbackup 1517 you didn't use -n flag with fbackup NFS . Do you use NFS ?
fbackup(3203): volume 1 has been used 35 time(s) Tape is used 35 times to backup on it

fbackup(3024): writing volume 1 to the output file /dev/rmt/0m says dat all files are backuped ( except 365544-36559) on your tape device
fbackup(3055): total file blocks read fbackup: 3308471 --> blocks are readed and ready to backup
fbackup(1030): warnings encountered during backup---> says you have number of warnings (365544-36559 )
fbackup(3056): total blocks written to output file /dev/rmt/0m: 3491891 ---> blocks they are backuped on your tape

I think your backup looks good.


Success


Idriz

Darren Prior
Honored Contributor
Solution

Re: Clarification on fbackup warnings...

Hi Phani,

I don't believe that the file number ties in with an inode number, I think it's more likely to be the position of the file within the list of files to be backed up.

regards,

Darren.
Calm down. It's only ones and zeros...
Cheryl Griffin
Honored Contributor

Re: Clarification on fbackup warnings...

Fbackup generates a list in memory of all files that will be written to the archive. If the files no longer exist or there is a problem with the file or filename when the archive is written to tape, then you will see a message such as this.

Recover the Index:
# frecover -I index

then determine what file is at the line numbers mentioned in the message.

SR 5003102814 is a request to have fbackup refer to the filename instead of index number.
"Downtime is a Crime."
Phani_4
Frequent Advisor

Re: Clarification on fbackup warnings...

Hi All,

I have tested on my server by following the below procedure....

1. Created files /etc/phani & /etc/varma

2. Initiated fbackup for /etc directory & removed the above two files by the time it started writing the files to the tape.

3. I observed the below warnings..for both the files /etc/phani & /etc/varma

fbackup(1102): WARNING: unable to stat file /etc/phani --> Since there is no file exists by this name while writing
fbackup(3005): WARNING: file number 398 was NOT backed up --> This file number 398 belongs to the above file

I got it....Hey thanx alot for your valuable information..:-)

Cheers,
Phani