fbackup error

[j773303]

Does anyone knows what happend on the fbackup?
Is it possible disk failure? Thanks.

fbackup(3009): WARNING: File number 83384 (/u3/rPOD02)
was not successfully backed up
fbackup(3009): WARNING: File number 83386 (/u3/rRBS1)
was not successfully backed up
fbackup(3009): WARNING: File number 83428 (/u4/rRBS2)
was not successfully backed up
fbackup(3009): WARNING: File number 83433 (/u4/rSYSTEM01)
was not successfully backed up
fbackup(3055): total file blocks read for backup: 196704900
fbackup(3056): total blocks written to output file /dev/rmt/0m: 196677323
fbackup(1030): warnings encountered during backup
logout

[Michael Tully]

These are warnings and not actual errors. The 3009 warning usually means that the file which was read into the backup list was not actually backed up. Generally this means that the file had been removed when fbackup went to backup the file. These normally happen for files in /var/tmp

[j773303]

But the 4 files are oracle db file, its still in the /u3 and /u4 directory. Does the fbackup(3009) WARNING ... means the file not backup to TAPE? Thanks.

[Michael Tully · Accepted solution]

Another meaning of the warning can be interpreted as the file(s) being in use at the time of the backup of the file(s) to tape (database on-line). The problem I see with this, is that if you tried to restore these files from tape, your database could end up being corrupted. The best way to backup a database is to have the database in 'quiescient' mode or have it shutdown completely when the backup is taken.

[Joseph Loo]

hi,

a few questions?

1) have u perform fbackup successfully for these db files?
2) is the database shutdown before fbackup begins running?
2) has the size of these files increase to more than what the tape can manage? size of your tape, please?

regards.

[Adisuria Wangsadinata_1]

Hi there,

It looks like when the backup was taken, the database still up & running. So the files (/u3/rPOD02, /u3/rRBS1, /u4/rRBS2, /u4/rSYSTEM01) still accessing by database process.

This warning message only, but will give you a problem when you try to restore these files into your database since the backup was not successfully backed up (can be a corrupted files).

To resolve this problem, you need to shutdown the database first before doing a backup. You can create the script to shutdown the database first and start the database after the backup finished.

Hope this information can help you.

Merry Xmas & Best Regards,
AW

[T. M. Louah]

They were excluded for some filesystem or tape IO issue .. mostly related to the fact that the files were open or some other process is pointing to them somehow ?? at the time of backup, you can talk to the developpers to make sure they open/close files correctly (if "fuser -u /u3" doesnot show the processes linked to the filesystem then troubleshooting this, ain't an easy task dude !)
.. I assume that u have shutdown DB then unmounted the filesystem & u've run FSCK on /u3 & /u4 it shows FS clean ?!
try to copy these file to a different filesystem (lvol) & run fbackup see if it works.
The other thing I can suggest is to try use -c config_file option with fbackup, there are more details in the manpages but create config_file with only these values:
blocksperrecord 128
records 128
readerprocesses 1
maxretries 10

Good Luck
Happy 2004 All

[Steven E. Protter]

Note:

Oracle db files can not be backed up by fbackup while the database is open. They will either be skipped or the backup will by fuzzy(oracles term) and not supported for restore.

I once did manage to restore a fuzzy backup because no database transactions had occurred since the database restart. I was extremely lucky and would not risk my job on such a backup again.

If you want fbackup to correctly back up an oracle database, it MUST be down.

Good luck.

SEP

[Bill Hassell]

This message tells you that files can't be read. If the files exist then a file or record lock exists (very normal for databases). fbackup honors file locks for good reason--the data is chanjging too fast for a valid backup. The files mentioned in trhe error messages have NOT been properly saved, which means you backup is NO GOOD. Don't use it to recover your Oracle database. Oracle (and most commercial database programs) offer a special backup mode where the changes are tracked separately during the backup, then posted once the backup is completed.

Just because a backup utility does not report an error message does not mean that the backup is valid. The changing records will cause database corruption after a restore. Carefull read the database manufacturer's documentation about backup and recovery. You must either: shutdown the database for the duration of the backup, or use a commercial backup tool like HP's Omniback (aka, Data Protector) and oreder the plugin's to support Oracle online backups.