1832981 Members
3314 Online
110048 Solutions
New Discussion

br_backup and fbackup

 
SOLVED
Go to solution
Ronelle van Niekerk
Regular Advisor

br_backup and fbackup

Hey guys,

I know that br_backup calls the fbackup command but I can't seem to find out any information on the usage of the br_backup command.

We're getting exit code = 2 errors on our backups on one server and I can't seem to figure out why. I'm hoping the -v option of fbackup will give me some more clues.

How do I get br_backup to call the fbackup command with the -v option?

And can anyone send me a doc or link with informtaion on the usage of br_backyup?

-Ronelle
rm -r /it/managers
3 REPLIES 3
Patrick Wallek
Honored Contributor
Solution

Re: br_backup and fbackup

br_backup is a script located in /usr/sam/lbin.

Have you checked in the /var/sam/log/br_log and /var/sam/SAM_br_msgs? Are you getting any e-mail from the backups? If not, you could add your e-mail address to the command line in cron.

Have a look at the br_backup script and it should be quite informative about how it works. It is documented very well internally.
A. Clay Stephenson
Acclaimed Contributor

Re: br_backup and fbackup

br_backup is simply a shell script in /usr/sam/lbin so you can add whatever options you like to the fbackup invocation. This really begs the question why are you using a backup utility that you really don't understand? Sam is quite good for some things but backups are too important to let someone else's script handle. I would explicitly code the script that invokes fbackup however you really want it to behave.
You should also note that br_backup logs its activity so you should be able to examine the sam logs. It's all in the br_backup script.

If it ain't broke, I can fix that.
Ronelle van Niekerk
Regular Advisor

Re: br_backup and fbackup

Thanks guys, I'll take a look at teh script.
Changed the e-mail in the crontab from nobody to root yesterday so I did get some more info on it.

The reason I asked teh question in the first place was that the /var/sam/log/br_log file didn't contain enough info. And the /var/sam/SAM_br_msgs file/directory doesn't exist.
rm -r /it/managers