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