On Jan 15, 2009, at 9:26 AM, John C Dury wrote:

ANR0481W Session 16603 for node <SERVERNAME> (WinNT) terminated
- client did not respond within 9000 seconds. (SESSION: 16603)

If TSM is struggling to get through the directories, then applications
associated with the data may be suffering the same problem.  This may
be the result of indifferent directory layout (far too many files in
directories) or disk hardware issue or contention or file system issue
(where chkdsk or equivalent might be run).  The hardware may simply be
underpowered for the amount of data involved (e.g., 5400 rpm disks or
perhaps older ATA pathing).  Or the file system type may be an
inefficient choice.  Large-scale data deployments cry out for a
knowledgeable data architect in order to be successful and to scale -
and that skill is often absent.

The owners of the data should be strongly advised to regard the backup
problem as a proportional indication of how very painful a file-
oriented restoral would be, where reconstructing Windows directory
entries is notoriously time-consuming.

   Richard Sims