I don't know if this is practical for everybody, but we send email about backups to our NT admins same as to the UNIX admins, using AIX sendmail. AIX sendmail can send mail to our EXCHANGE server. I'm not an AIX heavy, but I think my AIX guy just had to know the name of the Exchange server; it will receive mail from AIX sendmail, same as it can receive mail from any other external mail system coming off the internet.. I think that's true of most mail systems, not just EXCHANGE.
You can take several approaches to finding the right email address: For a large group of NT clients managed by one (group of) administrators, I put them in their own TSM domain. Then any machines in that TSM domain, I send the notification to that (group of) administrator's email address. You can also make a list of mail addresses/nodename pairs in a file, and have your ksh or perl script pick the mail address by looking it up in a file. Use the CONTACT field for NODENAME to store an email address, have your script look it up with SELECT when you need to send the owner mail. (This is probably the most practical if someone like your HELP DESK does your node name registration.) Just create AIX mail aliases for each nodename. Hope that helps? ************************************************************************ Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert ************************************************************************ -----Original Message----- From: Cheryl Miller [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 13, 2002 12:53 PM To: [EMAIL PROTECTED] Subject: Re: root required to kill TSM daemons? We are going to upgrade to Solaris 2.8 from 2.6 and we are also going to remove NetBackup from the TSM server, since it is still backing up some clients not yet converted. Per Tivoli's Level 2 this is what our TSM crashing is from: The problem you are seeing is caused by a limitation of the Solaris 2.6 OS. At that OS level, the SUN library had a hard-coded limit of 255 open/fopen calls allowed on the system at any given time. The SUN library can handle any combination of <255 open/fopen calls, but any fopen calls that exceed this limit will fail. Up to 1024 open calls can be made without any problems. Each disk volume (db, log, stgpool) defined to TSM will account for one open call. The fopen/open limit has been increased to 1024 in Solaris 2.7. Their are 2 problems that we are seeing that is causing us to have to bounce the TSM daemons on the client side. One is when the TSM server crashes and the backup is runnning, it will showed missed every day until the daemons are bounced. The other is a problem with the postschedulecmd in the dsm.sys. Tivoli told us that our e-mail notification script on unix is hanging sometimes when it goes out to check the status of the backup. This is confusing to me, because the script only checks the dsmsched.log? The 2 e-mail scripts we are using are attached. What are your shops using for e-mail notifications to DBAs/system admins. for the completion status of their backups on a daily basis? We don't have any solutions for NTs at all for this issue. Cheryl Miller Wells Fargo Bank Distributed Storage Management (DSM) 916-774-2073 -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 3:35 PM To: [EMAIL PROTECTED] Subject: Re: root required to kill TSM daemons? You know this started about NetBackup. I am wondering if they are aware that the same issues that NetBackup has are not issues on TSM. In NetBackup if the server crashes you have to restart all the media servers to get things to reconnnect. Maybe they are just presuming that it is the same with TSM. -----Original Message----- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 11:31 AM To: [EMAIL PROTECTED] Subject: Re: root required to kill TSM daemons? I agree. In the rare case our server is restarted or crashes, we do not have to restart the client schedulers. Only time I have seen it necessary to restart the clients is when someone has made network/DNS changes. -----Original Message----- From: Thomas A. La Porte [mailto:[EMAIL PROTECTED]] Sent: Monday, February 11, 2002 12:05 PM To: [EMAIL PROTECTED] Subject: Re: root required to kill TSM daemons? One solution is to simply cron a restart of the TSM daemons, however, the long term correct solution is to determine why your server is crashing. We go hundreds of days without restarting our TSM servers, and the only time we restart our client schedulers is when the include/exclude lists get updated. -- Tom Thomas A. La Porte DreamWorks SKG [EMAIL PROTECTED] On Fri, 8 Feb 2002, Cheryl Miller wrote: >Our company uses Powerbroker access instead of sudo and they don't want >to give us pbrun su-root privileges. Any other ideas? > >-----Original Message----- >From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]] >Sent: Friday, February 08, 2002 11:47 AM >To: [EMAIL PROTECTED] >Subject: Re: root required to kill TSM daemons? > > >Pl look at sudo command acts as proxy for root only for that cmd. >BALANAND > >-----Original Message----- >From: Cheryl Miller [mailto:[EMAIL PROTECTED]] >Sent: Friday, February 08, 2002 12:41 PM >To: [EMAIL PROTECTED] >Subject: root required to kill TSM daemons? > > >We just converted to TSM 4.2.1.9 from NetBackup. We are finding that >our group needs to be able to stop the TSM daemons and start the start >up script, instead of always having the system admin. do this. Right >now I am told that there is no work around for root privileges being >needed to kill the TSM daemons. I'm wondering how other shops get >around this problem? When >our TSM server crashes, all of the clients that are getting backed up >are getting hung schedulers and need to be bounced to resume working. >The fact that root privileges are needed to bounce the daemons is >adding on days to our resolution, since we have to open a problem >ticket with the system admin. group and wait for them to bounce the >daemons. We have ids on most of >the unix servers and could do it, if the permissions allowed. > >Any ideas?? Do any of you have a work around for this problem? Tivoli >had me >open an enhancement request. > >....Cheryl > >Cheryl Miller >Wells Fargo Bank >Distributed Storage Management (DSM) >916-774-2073 > >
