fbackup error

[someone_4]

I got this backup error email attached. I also added the /var/sam/log/br_log.How would I go about fixing my full back up?

Richard

[Sanjay_6]

Hi Richard,

Seems like the file is in use and because of that it is not being backed up.

Hope this helps.

Regds

[Sridhar Bhaskarla]

Hi Richard,

It's better to exclude temporary directories in your backups using -e option either in command line or in the graph file.

-Sri

[Kurtkarl]

hi,

It's seems that those are netscape logs files which are currently open and being accessed.

Try excluding those by creating graphs as posted by others.

Thanks
Joey

[someone_4]

how is that done though sam? If it cant be done though sam how do i do that though the command line?

Richard

[someone_4]

Am I even doing the right type of back up?
What kind of backup should I be doing?

Richard

[Sachin Patel]

Hi Richard,
try to write on that tape using tar first.
Also can you use /dev/rmt/?m rather then *DDS.

tar cvf /dev/rmt/?m /home/richard/*.*

Sachin patel

[S.K. Chan]

Some example (say you want to do a full backup everything in / but exclude /tmp). Assuming yr device is /dev/rmt/0m

# fbackup -f /dev/rmt/0m -i / -e /tmp
OR
# fbackup -f /dev/rmt/0m -g /tmp/graph
==> Create file "graph" in /tmp and put these in it :-
i /
e /tmp

[Sridhar Bhaskarla]

Hi Richard,

I heard you talking about Omniback. How far are you?.

You are doing the right thing if you don't have third party backup softwares. Fbackup is the good solution.

man fbackup and then doing some R&D will help you a lot.

A graph file is basically a file that contains the directories to be excluded or included

For ex., if you have a graph file that has the following syntax

i /
e /netip/netscape/direct4/slapd-192.168.10.65/logs
e /tmp
e /var/tmp


#fbackup -g /tmp/graph -f /dev/rmt/0m

Will take full backup of the system excluding the directories you specified in the graph file.

Try man fbackup for more details

-Sri

[Kelli Ward]

Another shortterm possibility, if a back-up is mission critical would be to reboot your system and boot up single user (use mount -a after boot up if you have an LVM file system) run sam on the command line and perform your back up. This can get you a fresh current back-up while you explore long term repair possibilities and what is cauing the failure will most likely not be running.
Best of luck.
Kel

[Mark Vollmers]

Richard-

I had a similar experience a while ago, and I am trying to remember the specifics. In my case, during backup, the RAID went whacky and went down on me. The log was filled with a ton of messages, but I don't remember what they said. This might not be the case here, but check the syslog for any SCSI type errors and make sure that you can move around to all the directories. Like I said, it might not apply, but worth checking.

Mark