kicking Tivoli Storage Manager (TSM) in the pants, remotely (and silently!)

Tivoli Storage Manager (TSM) can be quite unfriendly at my place of work, especially when it requires one to re-associate backup routines and restart services in order to get its Client Acceptor Daemon and scheduler to work properly after a TSM server outage. In past scenarios this was a manual process, requiring a technician to visit a users desk and run through the GUI setup wizard in the TSM client. However, following these commands, one can kickstart TSM into properly scheduling itself by re-associating it with the TSM backup server, remotely and more importantly, silently. We use SCCM and it’s suite of right-click tools to open an interactive command prompt on the client.

Cd c:\Program Files\Tivoli\TSM\baclient
Dsmcutil.exe install cad /name:”TSM Client Acceptor” /node:<PC name> /password:desktop /autostart:yes
Dsmcutil.exe install remoteagent /name:”TSM Remote Client Agent” /node:<PC Name> /password:desktop /partnername:”TSM Client Acceptor”
Dsmcutil.exe install scheduler /name:”TSM Scheduler” /node:<PC Name> /password:desktop /autostart:yes
Dsmadmc.exe –id=<TSM admin username> –pa=<TSM admin password> upd node <PC Name> desktop passé=0
Dsmcutil.exe updatepw /node:<PC Name> /password:<TSM client password> /validate:yes
Dsmadmc.exe –id=<TSM admin username> –pa=<TSM admin password> def assoc workstation <backup type ex: NON-KEY-MGM> <PC Name> 
Net stop “TSM Client Acceptor”
Net start “TSM Client Acceptor”
Net stop “TSM Scheduler”
Net start “TSM Scheduler”

Obviously replace the items in the < > tags with your own information. You can then view the dsmsched.log file, located at C:\Program Files\Tivoli\TSM\baclient (on Windows 7) to see that the scheduler is once again started and has the proper information to back up the client.


About this entry