automated back up problem

UNIX for Beginners Q & A UNIX for Dummies Questions & Answers
1

Hi..
I am using HP UX 11.0

i want to make automated back up from SAM back up tool....

so i mentioned the file systems and back up device /dev/rmt/0m and time 0:00 and days of the week........

but it was not successful.....the back up job was not started on specified time.....

i am in doubt if any thing else i have to do........

please suggest....

thanks
Praful

2

When you use SAM to setup a backup, it creates some files and set up a cronjob for you. Look in root's crontab to see if it got added. I just used SAM to setup a backup on HP-UX 11.0. The job is "/usr/sam/lbin/br_backup...." So was that job added to your root's crontab? Is cron running? My job says it will write logs to /var/sam/SAM_br_msgs so I would check that file. If the cronjob exists, it probably tried to run and wrote some error messages.

So the things to check are:

1) did SAM install a cron job?

2) does /var/adm/cron/log say if the job was attempted?

3) what errors are in the job's own logfile?

3

Perderabo,

I believe that the path is /usr/lib/cron/log for the CRON execution log on HPUX 11.x.

I know it is a nit-picky item, but might save Prafulla some time.

Also, Prafulla, while in SAM I think you can view the SAM log after it executes your commands under OPTIONS --> VIEW SAM LOG. It has time parameters and other options you can set.

:smiley:

4

Now that I think about it, there is a much more reliable way to edit the crontab for root.

execute these commands.

crontab -l > tempcron
vi tempcron
crontab tempcron

This is easy and safe and you always have a copy of your CRON in case you accidentally blow it away.

:slight_smile:

5

No, /var/adm/cron/log is the correct path. It moved starting with hp-ux 10.x. However /usr/lib/cron is a symlink to /var/adm/cron for people who are used to the old path. HP does want us to start using the real path since the symlink may disappear in the future.

6

Thanks for the update. I was not aware of that change.

7

Hi.....

This is the crontab -l

30 23 * * 1,3,5 /usr/sam/lbin/br_backup DAT FULL Y /dev/rmt/0m /etc/sam/br/graph
XCAa02548 arbor1 Y 1 N > /var/sam/SAM_br_msgs 2>&1 #sambackup
30 23 * * 2,4 /usr/sam/lbin/br_backup DAT FULL Y /dev/rmt/0m /etc/sam/br/graphUF
Aa02548 arbor Y 1 N > /var/sam/SAM_br_msgs 2>&1 #sambackup

THIS IS /VAR/ADM/CRON/LOG

root 12102 c Tue Nov 20 23:30:00 IST 2001
root 12102 c Tue Nov 20 23:30:37 IST 2001 rc=4

AND IF U SEE THE BKPLOG IT IS ONLY SHOWING ONE LINE

2048 0/

when i am trying to see the listing frm tape....

frecover -f /dev/rmt/0m -I /tmp/bkplog

it is showing the same one line 2048 0/

IS THIS THE COMMAND TO SEE THE LISTING?

now if i don't want to make the backup by SAM tool wht i have to do make it run at a specified time?

i have to just edit crontab -e and put the timing in proper faomat....that's all...or i have to run any specific demon..

please suggest
prafulla

8

First, notice the "> /var/sam/SAM_br_msgs 2>&1 ". This tells you that the answer to why your script only ran for 37 seconds should be in /var/sam/SAM_br_msgs.

The frecover command that you used should show the index on the tape, but with a run of only 37 seconds, it's improbable that fbackup even attempted to write one.

Yes, I would just write a script that invokes fbackup. Once I had the script running manually, I would put it in crontab. fbackup does not rely on any daemons for local work. If you backup nfs files, then you will need nfs daemons.