Backup Problems

[Carter Jay]

Hello,

I have a very annoying problem when i try to make automated backups with sam (full or incr).
Everytime, I launch the bck at 23:00, at 10:00 o'clock in the morning, it's still running and using 98% of CPU (top). I've got this error message in logfile, after I kill all the fbackup processes.
Full backup started on manon : Fri Aug 23 23:00:00 WETDST 2002 (Schedu
{ fbackup -0 -u -g /etc/sam/br/graphHDAa10202 -I /var/sam/log/br_in
Full backup failed on manon : Mon Aug 26 15:36:53 WETDST 2002 .
Exit code = 137
I've syserr in the consoles telling me that /var is full (and it is), perhaps the size of log files.
It seems to impact tables ASCII fields in some Oracle instances too.

Here are the patch i've installed on the box.
PHCO_21494
PHCO_23262
PHCO_23436
PHCO_25418
PHCO_25424
PHKL_21392
PHKL_22145
PHNE_20316
PHSS_21947

Thanks in advance for your help

Jerome

[Stefan Farrelly]

If you keep filling up /var because of the fbackup index file (which lists every file backed up so it can be huge!) then either remove the -I option or change it to another filesystem where you do have space, or increase /var.

[Carter Jay]

Also, I've got the file:
SAM_br_msgs full of:
br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1004): session begins on Fri Aug 23 23:00:00 2002
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
/usr/lib/dld.sl: Unresolved symbol: acl (code) from fbackup
and it is
rw-r--r-- 1 root sys 1778367488 Aug 26 10:41 SAM_br_msgs

Thanks in adavnce again

Regards

Jerome

[Donald Kok]

Hi Jerome,
fbackup creates files in the /var fs. Since this is full, fbackup can not do its job.

There are several paths to follow:
- remove some files from /var (f.i. look at /var/tmp and /var/spool)
- You can extend /var. If you have onlinejfs, you can do this online. Otherwise you need to go to single user mode. (And you have to have some diskspace, of course)
- you can create an new file system and mount this somewhere under /var, say /var/tmp. Now your /var/tmp files will not fill /var.

The first options is the easiest, but not always possible. you can use the command `du -ks * | sort -nr` to find out which dirs take the most diskspace.
Goodluck
Donald

[Stefan Farrelly · Accepted solution]

Heres a message with the same problem and the resolution;

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x8d6637f45ef7d4118fef0090279cd0f9,00.html