As I understand it, TSM clients run two sessions: a control path and a data
path.  We don't see either of the sessions hanging around if the scheduler
is used to run backups.  If the client runs from the GUI, and doesn't close
the GUI, the control session hangs around - in our instance for 60 minutes,
until timeout.

I have some Solaris clients who have erroneously re-spawned new sessions
repeatedly (from inittab).  Those need fixing.


At 10:06 AM 5/10/01 -0400, you wrote:

does anyone have problems with your clients creating multiple sessions
during incremental backups? in our case they create multiple sessions for
each client and they all seem to get hung up until morning. ANy ideas or
suggestions would be great.

the server is 4.1.3 and clients are 3.7. to 4.1