Fawad, have you run a sample backup and gathered an instrumentation trace?
This would be a good place to start to try and determine where a bottleneck
might exist. To gather this, place the statement "testflag
instrument:detail" in the dsm.opt file and run the backup. Perhaps if you
do this and post the output of the file (named dsminstr.report for Novell)
to the listserv, members of the listserv (and I)  could look at the result.
We also would need to know much more about your environment that you have.
I would also suggest opening up a PMR with IBM Software support. They will
send you a performance questionnaire and gather the appropriate traces that
they would need to look at the performance problem you're having.

At 02:00 PM 12/4/2006 -0500, you wrote:

Hi All,

Im looking for known issues, pertaining to TSM client 5.2.3 and
Novell/Netware environments, where the TSM incremental backups may
hang for not so obvious reasons. We have already eliminated network
problems as being the cause. Are there any technotes, incidents that
anyone is aware of that might hint of cause/solutions for this
scenario. Im looking for anything and everything at this point as we
are experiencing very very slow backups for some of our Novell
clients. The data has also increasing but the window which the backups
take, have increased on much larger span, so it is hard for us to
point that as the root cause. Novell Client is at 5.6
Thanks in advance guys.
--
Regards,

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