1847225 Members
2463 Online
110263 Solutions
New Discussion

Re: fbackup problem

 
Mauro_3
Advisor

fbackup problem

Hi,
I?m trying to backup my system with fbackup, and sometimes it doesn?t works well. In History Log it gives me a message and a Exit Code = 2. I read the manual and saw that a problem occur and the backup didn?t finish, but what problem ? How can I know what is my problem ? Is there a Log of problems ? I?m think the problem is the space in the tape. How can I see the free space in a tape ?
Thanks,
Mauro
4 REPLIES 4
Mark Vollmers
Esteemed Contributor

Re: fbackup problem

Mauro-

What message did backup give to you? If the tape filled up, it should stop and say something like "insert next tape and hit enter" If you have the job on cron, it will exit but you should get email with the message. Are you running through SAM or a command prompt. SAM has a log for backups in /var/sam/log/br_log. It could be a number of things. Also, is there anything odd in the syslog at the time that backup was running? Let us know if you find anything.

Mark
"We apologize for the inconvience" -God's last message to all creation, from Douglas Adams "So Long and Thanks for all the Fish"
Mauro_3
Advisor

Re: fbackup problem

Hi Mark,
I running it with SAM with the fbackup command.
I try to find something in the logs you told me, but I could not find anything about errors in the backup. How can I see the free space in the tape ?

Thanks guy,
Mauro
Mark Vollmers
Esteemed Contributor

Re: fbackup problem

Hi, Mauro,

I don't think you can see the free space on the tape. SAM is probably set up to rewind after finishing, so when you run it will start at the beginning, as opposed to appending to the current volume of the tape. This means that the only free space that will matter will be the capacity of the tape. what type are you using (DDS-3, DDS-2, etc)? the DDS-3 tapes have a 24 GB compressed limit. How much data are you backing up? If a full backup, run bdf and add up the volume groups to get a rough idea. Since you are running through sam, you can open up SAM and go to backup. select the tape device and there should be a view logs option up in the toolbar. You can view the br_log, although that might just tell you that it failed. Do you have it cron'ed (or scheduled)? If so, it will email root the messages. Otherwise, you could run it again and get the error messages from the pop-up window as it runs. If it wants a second tape, you can stick it in then.

Mark
"We apologize for the inconvience" -God's last message to all creation, from Douglas Adams "So Long and Thanks for all the Fish"
Sachin Patel
Honored Contributor

Re: fbackup problem

Hi
Try to run from command line and you will have complet control.
#mkdir /usr/adm/fbackupfiles/
#cd /var/adm/fbackupfiles/
#touch date
#touch fbackup.log (you can use to redirect your output here from script)
#touch fbackup.datestamp
#date > fbackup.datestamp
#touch graphs
#vi graphs
i / (you are including / filesystem)
e /tmp (exclude /tmp)
e /cdrom (exclude /cdrom)
e /nfs (exclude nfs file systems) and so on....
#fbackup -0vug /var/adm/fbackupfiles/graphs -f /dev/rmt/c?t?d? (0= level, v=verbose, u=update dates file and timestamp and more, g=use graph file)

This will gives you all in verbose mode. You can skip all this file touching things and just run this command. you can create your graph file anywhere else.

Sachin
Is photography a hobby or another way to spend $