Sunday, July 09, 2006

Help! Problem With Shared Library Client!

Ok, here is my problem.  I have a large shared library that supports 5 TSM servers. All of the TSM servers, save one, run without any problems. The one with problems is pathed to 32 of the 5 drives (they are designated just for its use) and periodically its mount requests go into a RESERVED state but never mount.  I have tried FORCESYNC'ing both sides to see if it was communication but that didn't work.  I have tried setting paths offline then back online and that didn't work either. The only thing that works is to cycle the TSM server then it comes back up and starts mounting tapes like nothing was wrong.  This happens on average every 24-48 hours.  This is a large DB client TSM instance so the reboots are hurting critical business apps backups. I don't see any glaring errors in the activity log or in the AIX errpt. Any suggestions would be gladly received.


  1. I have only one idea: do they have the same TSM version?

  2. Actually that was my last resort. I figured someone would say it. The 4 servers are and the DB one is Why the .4 update or lack of it would cause this is crazy but we have seen stranger things happen with TSM. I was hoping it was something I missed because getting an upgrade on that server is a nightmare. The DBA's don't like giving me more than 1 hour to do a change and if I run into complications all hell would break loose.

  3. Do that upgrade and I think that will solve your problem.
    I am curious to know the result.
    So are you brave enough to do that?

  4. I agree with Chad that all of the servers should be be at the same level. The other thing that you could try is update the library and set RESETDrives=no.