TSM Client Configuration to be checked:
c:\Program Files\Tivoli\tsm\baclient\
check for the 'dsm Opt' file and 'dsmshed' in the folder, If present check the Opt file , Open with txt(notepad), and check if the Ping is working for the tsm-server.
If yes,
Then check for the services.msc and check for tsm acceptor service and tsm scheduler service both should be in 'Automatic' and should be in started mode.
if yes,
Then open the dsmshed.log file in the location c:\Program Files\Tivoli\tsm\baclient\ and check if the client has a valid scheduled time/window to get backup.
if yes,
Then the backup should be working else we need to involve Unix team and Netwok team for Further investigation.
TSM Client Services to be checked:
Go to start->settings->control panel-> and then click on services.
1.tsm_acceptor
2.tsm_scheduler
If the server is a NT with SP4/6 and if you are not able to start the service then you need to restart the server(thats a bug in have faced problems, reboot is ultimate globle solution).
TSM Client configuration:
1.Configuring the TSM client after installation tsm client appliation, select new Opt file.
:)
Known issues:
1. The TSM services will be in stop state
Resolution: go to services.msc and start them.
2 The TSM services will not start.
Resolution: Stop the acceptor and sheduler service and try starting it one after the other.(in case of NT and has very minimal resources - CPU, memory , Pagefile etc.
else user Windows "Process explorerer" and kill the Tivoli dms processes and try starting the services.
3. if option 2 fails completely in starting the services, agree with management to get the server in maintainance mode and on approval reboot the server.
4. if option 3 doesnt work, tru uninstall reboot, and reinstall and reboot/reconfiguring.
Cheers!
Very Important:
1.When u r taking hand over from other member wrt tsm server, Make sure u check the dsm.opt file as it may contain inclusion and exclusion list,
with regards to the database, there will be a database plugin installed with SQL, make sure the Datbase team and urself verify the backup on regular basis.
2.if sql plugin in installed you generally exclude the .mdf, .ldf , .bak, .bkf files, make sure if u need to add anyof the selections for database / file system, .bkf files.
3.Generally you get TCP /IP errors while doing restoration or a manual backup:
Make Sure the TSm server is ping able, reachable, and is working fine. iF not check with network and UNIX team for more assistance.
4.one big pain is the connectivity issues for tsm server, as the tsm server is a AIX box and works on session bassis you will need your windows client to establish session ping-ing to the tsm server for the restoration, there might be a bud in the tsm server NIC configuration which needs to be fixed. Once the ping is established the session will be continuous and will be stable.
5.second big pain is that the tsm server from unix side needs to be properly maintained.
The disk pool needs to be monitored continuously and the scratch tapes also needs to be monitored.
TSM_server takes incremental backup from windows/unix clients and writes that on the disk pool(loca disks which are are hardware raid), once the data is old/archived, the tsm server will write that on the the tapes and those will be sent to offsite.
Improper maintainance will lead to the disk pool to fill and hence the nightly scheduled jobs and restorations will be failed.
