Indeed it is too bad TSM (or Veritas or Legato) doesn't supply a
notification mechanism.  It's pretty simple for our UNIX clients to notify
themselves, but for others, not so easy.

We load a DB2 database every morning with info from TSM server databases
(we've got 8 servers).  Then we run a script that checks filespaces backup
completion times/dates, and send e-mail to the owner of the node, getting
addresses from owner - employee information system.

Not fail-safe, but it helps


At 01:03 PM 3/15/01 -0500, Prather, Wanda wrote:

Part of the problem is, who is the "user".

Under WinnT, scheduled backups generally run under the System account.  Any
USER account may or may not be logged on at the time backups are run.  On
UNIX, the backups generally run as root.

What we do is query the eventlog on the server end, and generate mail
messages to be sent to users whose backups fail or miss.  That works if you
have a way to map the TSM node names into mail ids.  But, it doesn't take
into account any individual files that fail to back up, we really don't have
a solution for that yet.



-----Original Message-----
From: Rajesh Oak [mailto:rajeshoak AT LYCOS DOT COM]
Sent: Thursday, March 15, 2001 12:37 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: client notification


Everyone,
Can we notify a client that the backup was successful/not successful after
the backup schedule finishes. Say a screen pops up with the message "
Backup's done" or anything thing else which sends a signal to the user about
the Satus of his backup.

Regards.
Rajesh Oak


Get 250 color business cards for FREE! at Lycos Mail
http://mail.lycos.com/freemail/vistaprint_index.html