topic Re: Mail from SAM Backup in Operating System - HP-UX

Mail from SAM Backup

Guy Humphreys — Thu, 08 Apr 2004 06:58:53 GMT

Hi All,

I have a 10.20 machine that runs a SAM created backup everynight. It used to just email root with the results upon completion but now we want it to email to an internet address.

I have altered the file:

/var/spool/cron/crontabs/root so that instead of it going to root only it goes to:
helpdesk@mycomp.com,root

However, the internet address never receives the mail but the usual local root mailbox does. If I do a manual:

mailx -s "subject line" helpdesk@mycomp.com,root < /somefile

both recipients get the mail OK, so I know sendmail is working OK

Does anyone have clue why it is behaving oddly, or a workaround perhaps

Thanks a lot
Guy

Re: Mail from SAM Backup

Steven E. Protter — Thu, 08 Apr 2004 07:03:53 GMT

This methodology works for me.

change
mailx -s "subject line" helpdesk@mycomp.com,root < /somefile

to

/somefile 2>&1 | mailx -s "subject line" helpdesk@mycomp.com,root

SEP

Re: Mail from SAM Backup

RAC_1 — Thu, 08 Apr 2004 07:15:35 GMT

mailx -s "subject line" helpdesk@mycomp.com,root < /somefile

should work. Does the email for helpdesk sits in mailq? What do you get in mail.log?

You can try as follows.
echo "some_file"|mailx -s "" helpdesk@mycomp.com, root

Anil

Re: Mail from SAM Backup

Guy Humphreys — Thu, 08 Apr 2004 08:26:12 GMT

Thanks for the quick responses guys, however I don't think I have explained myself properly.

The mailx command I mention above works for me, I only used it to check that sendmail was working. What is NOT working is the sam backup email notification. the backup is triggered from cron as below:

00 1 * * * /usr/sam/lbin/br_backup MAG FULL Y /dev/rmt/1m /etc/sam/br/graphXBAa12086 helpdesk@comp.com,root Y 1 N > /var/tmp/SAM_br_msgs 2>&1 #sambackup

the fbackup jobs runs and emails the results to root but does not email them to the internet address helpdesk@comp.com

When you suggest altering my mailx line do you mean the script within br_backup? I am reticent to go 'mucking' about with this HP script (unless of course there is no other course of action)

Thanks again
Guy

Re: Mail from SAM Backup

John Kelly_3 — Thu, 08 Apr 2004 08:36:26 GMT

The root mail you receive is where cron sends the job's output - so just redirect all output from the cron job to a mail to your helpdesk account. E.g.

00 22 * * * /sam/backupcommand > /usr/bin/mailx -s "Backup report" helpdesk@mail.com 2>&1

Re: Mail from SAM Backup

John Kelly_3 — Thu, 08 Apr 2004 08:43:41 GMT

Sorry, that should be a | not a >
E.g.
00 22 * * * /sam/backupcommand | /usr/bin/mailx -s "Backup report" helpdesk@mail.com 2>&1

Re: Mail from SAM Backup

Guy Humphreys — Fri, 30 Apr 2004 03:05:28 GMT

Thanks for the quick replies guys, Sorry this msg is so late, I have been working on other things.

Have not managed to implement your suggestions as the problem seems to have disappeared on its own!!! Issue must have been elsewhere.

Cheers
Guy

Re: Mail from SAM Backup

Darren Prior — Fri, 30 Apr 2004 04:11:04 GMT

Hi Guy,

The br_backup script states that the argument $6 is for the user that should be sent email, rather than a list of users. You could modify the script, as you are aware it would no longer be supported by HP - and it's possible that patching could overwrite your changes.

regards,

Darren.

Re: Mail from SAM Backup

Guy Humphreys — Fri, 30 Apr 2004 04:19:49 GMT

I think I have it, did not realise that argument $6 could only have one user and not a list - Thanks for pointing that out Darren.

How about I use an alias instead? Think that should work

Cheers
Guy

Re: Mail from SAM Backup

Darren Prior — Fri, 30 Apr 2004 04:32:25 GMT

Yes - that sounds a better solution. You could probably rewrite the script to cope with a list, but the alias idea is neater. Once you start modifying system scripts it can be pretty easy to forget just which ones have changed!

regards,

Darren.

Re: Mail from SAM Backup

Tapas Jha — Fri, 30 Apr 2004 04:35:52 GMT

Hi,

Just looking your mail it seems everything is perfect except the cron file you have modified. I think you have manually modified the cron. Either Do crontab -e or restart the cron. If you do manually modification then cron will take previous one.

Rgds
Tapas