[ADSM-L] TSM 5.4 Performance Issues

        This message is in regard to the posts that have been made
recently to the ADSM listserv regarding performance issues resulting from
upgrading the TSM client to V5.4. After discussing this with Andy and other
developers at IBM, we have the following information regarding this issue:

        The APAR for this performance issue that has been opened is
IC53531. Initially, this APAR was only opened for the NetWare platform, but
the APAR will now be updated to include additional platforms in addition to
NetWare. This APAR affects ALL 5.4.1 and 5.5.0 levels on ALL client
platforms (including Mac OS 10.x) except Windows. The fix for this APAR is
for the client only. There are no TSM server fixes needed for this APAR.

        The description of the APAR is as follows:

TSM Performance Degradation after upgrade to client 5.4.1 or 5.5.0 on all
platforms except Windows. TSM backup times increase dramatically after an
upgrade to the 5.4.1 or 5.5.0 TSM client.

If a client instrumentation trace is take for the client (using testflag
instrument:detail), statistics will show the busiest thread spending a
majority of the time being spent in the "other" category.

This APAR affects ALL client platforms except the Windows platform at the
5.4.1 or 5.5.0 levels. This includes the MAC OS 10.x client as well.

        This APAR will be fixed at the following levels:

        For the NetWare client platform, an interim fix (level 5.4.1.4)
has already been released.

        For all other platforms, customers have several options:

        A fully tested fix will be delivered at levels 5.5.1.0 and
5.4.2.0. TSM client level 5.4.2.0 is scheduled to be available around the
end of this month (3/2008), and level 5.5.1.0 is scheduled for availability
around the end of June (6/2008). (These dates are tentative, and subject to
change depending on testing that is being done).

        There also will be interim fixes available for all affected
platforms for TSM V5.5. The interim fix 5.5.0.6 is scheduled for
availability around the end of this month.

        There have been questions raised from customers on how to tell if
a client is affected by this APAR. If a client has many (millions of files)
has been recently upgraded from 5.3 to 5.4.1 or 5.5.0, and has noticed a
significant change in the backup time, this APAR may apply. If a client
instrumentation trace is taken on the client (using testflag
instrument:detail) the instrumentation trace will indicates a majority of
time in the "other" category for for the busiest thread for an affected client.

        If there are additional questions regarding this APAR, please
reply to this post or you can also send emails to my IBM email address at
ddcanan AT us.ibm DOT com.




Dave Canan
TSM Performance
IBM Advanced Technical Support
ddcanan AT us.ibm DOT com