I'm going to assume you're talking a TSM 3.7 client...
I have seen this at a client site where their idletimeout was set too low.
These second sessions you're seeing are from the RESOURCEUTILIZATION which
defaults to 2. TSM will start a session for session communications and
another for transferring the data. While the 2nd session is backing up a
filespace, the 1st session sits idle. If the IDLETIMEOUT is reached before
the 2nd session has finished backing up the filespace, the 'communication'
session (1st session) is cancelled and the remaining filespaces are not
performed, or the stats are not transmitted.
Try bumping up your IDLETIMEOUT on the server.
Bill Boyer
DSS, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Lawrence Clark
Sent: Sunday, October 08, 2000 3:01 PM
To: [EMAIL PROTECTED]
Subject: A 3.7 bug?
Here's another peculiar event sequence that's showed up since upgrading the
server for backups that do not occuring thier window:
1). Backup occurs past the window time (o.k.)
2). Just as the backup is completeing a second session appears to attempt to
start.
3). The original sessions completes reporting it's backup stats.
4). An error message is generated saying it cannot start the session since
one is in play for the client.
5). The 1st sesion completes
6). The second session terminates
I've seen this for nodes that complete past thier window and the new session
attempts to start just as the previous one is completing ( but not
complete).
There is only one instance of the sched process running on the AIX client.
Anyone seen this?
10/8/00 6:13 ANR0403I Session 6339 ended for node TOLLDBMS (AIX).
10/8/00 6:13 ANE4952I (Session: 6385, Node: TOLLDBMS) Total
number of objects inspected: 65,050
10/8/00 6:13 ANE4954I (Session: 6385, Node: TOLLDBMS) Total
number of objects backed up: 2,875
10/8/00 6:13 ANE4958I (Session: 6385, Node: TOLLDBMS) Total
number of objects updated: 0
10/8/00 6:13 ANE4960I (Session: 6385, Node: TOLLDBMS) Total
number of objects rebound: 0
10/8/00 6:13 ANE4957I (Session: 6385, Node: TOLLDBMS) Total
number of objects deleted: 0
10/8/00 6:13 ANE4970I (Session: 6385, Node: TOLLDBMS) Total
number of objects expired: 3,965
10/8/00 6:13 ANR0406I Session 6386 started for node TOLLDBMS (AIX)
(Tcp/Ip 129.9.199.18(32950)).
10/8/00 6:13 ANE4959I (Session: 6385, Node: TOLLDBMS) Total
number of objects failed: 0
10/8/00 6:13 ANE4961I (Session: 6385, Node: TOLLDBMS) Total
number of bytes transferred: 768.53 MB
10/8/00 6:13 ANE4963I (Session: 6385, Node: TOLLDBMS) Data
transfer time: 18,281.65 sec
10/8/00 6:13 ANE4966I (Session: 6385, Node: TOLLDBMS) Network
data transfer rate: 43.04 KB/sec
10/8/00 6:13 ANE4967I (Session: 6385, Node: TOLLDBMS) Aggregate
data transfer rate: 42.17 KB/sec
10/8/00 6:13 ANE4968I (Session: 6385, Node: TOLLDBMS) Objects
compressed by: 0%
10/8/00 6:13 ANE4964I (Session: 6385, Node: TOLLDBMS) Elapsed
processing time: 05:10:59
10/8/00 6:13 ANR0403I Session 6385 ended for node TOLLDBMS (AIX).
10/8/00 6:13 ANR2576W An attempt was made to update an event
record for a scheduled operation which has alr eady been executed -
multiple client schedulers may be active for node TOLLDBMS.
10/8/00 6:13 ANR0403I Session 6386 ended for node TOLLDBMS (AIX).
10/8/00 6:13 ANR8336I Verifying label of 3590 volume 000159 in
drive 3590RMT1 (/dev/rmt1).
10/8/00 6:13 ANR0406I Session 6387 started for node TOLLDBMS (AIX)
(Tcp/Ip 129.9.199.18(32951)).
10/8/00 6:13 ANR0403I Session 6387 ended for node TOLLDBMS (AIX).
