The answer is, because they do.
I thought this started with the 3.7 client, not the 3.1.0.7 client, but I
can't swear to that.
The client now starts 2 sessions, the data flows on one, the control
information flows on the other.
The client may actually start MORE than 2 sessions, if it decides the system
has enough resources.
There is a parm that can be used to control it somewhat. Look up the CLIENT
option
RESOURCEUTILITZATION.
-----Original Message-----
From: Brazner, Bob [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 12, 2001 11:48 AM
To: [EMAIL PROTECTED]
Subject: Why do backups have two sessions?
Many of my nodes appear to always initiate two sessions whenever I do a
backup. It appears all the client data is being transferred to the TSM
server via one of the sessions (as I would expect). The other session just
sits in "IdleW" status and racks up a few hundred or thousand bytes
sent/received. Occasionaly, I'll see a situation where, let's say, 2K
bytes have been received, but 10 times that have been sent. Can anyone
tell me what this second session is doing? Does it have something to do
with "client owner"? Note, we do not run the web backup-archive client.
System is recently TSM 4.1 (on AIX 4.3.3), but I noticed this happening on
ADSM 3.1.2.0. Clients I've seen this on range from 3.1.0.7, to 3.7, to
4.1.2. Please cc me directly on any reply to the listserv. Thanks.
Bob Brazner
Johnson Controls, Inc.
(414) 524-2570
[EMAIL PROTECTED]
