Richard,
More info on your question, taken from Redbook SG24-5477-00
Multi-session client operation
The new multi-session function is completely transparent to the user. There
is no
need to switch it on or off; it starts automatically. The Tivoli Storage
Manager
client decides if a performance improvement can be gained by starting an
additional session to the server.
The client determines the number of started sessions to transfer the data
according to the speed of the current workload.
The multi-session function involves three types of threads: compare, data
transfer, and monitor.
? Compare thread
The purpose of the compare session is to generate a candidate list of files
that
have to be transferred to the Tivoli Storage Manager server (backup or
archive). As soon as one transaction limit is reached, the list with the
files for
that one transaction will be handed over to a data transfer thread. The
compare thread starts a session to the Tivoli Storage Manager server of the
type node. There can be one or more compare threads at the same time.
? Data transfer thread
A data transfer thread is responsible for the file I/O, the compression,
and
sending the data and waiting for the commit of the transferred data. The
data
transfer thread starts a session to the Tivoli Storage Manager server of
the
type node. There can be one or more data transfer threads at the same time.
? Monitor thread
The task of this thread is to monitor whether the backup or archive
operation
could speed up if more data sessions were to be started, so that multiple
data
sessions could run at the same time. The monitor thread does not open a
separate session to the Tivoli Storage Manager server.
The design of the function is to have one thread creating transactions (the
compare thread) and one or more threads reading the files from disk and
sending
data to the server, each with its own session to the server. The monitor
thread
decides how many sessions should be used.
The advantages of this implementation are good load balancing capabilities
(can
be used on a single file specification) and (estimated) good performance
gains on
backups that send large amounts of data to the server.
Gabriel C. Wiley
ADSM/TSM Administrator
AIX Support
Phone 1-614-308-6709
Pager 1-877-489-2867
Fax 1-614-308-6637
Cell 1-740-972-6441
"Dearman, Richard" <rdearm1 AT UIC DOT EDU>@VM.MARIST.EDU> on 11/12/2001
06:57:45
PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: confused
Why is it every time I backup a server my q sess output at my tsm server
shows my send bytes going up as well as my recvdbytes. I'm not doing a
restore to the node so shouldn't only my recvdbytes statistics go up.
125,581 Tcp/Ip IdleW 2 S 81.0 M 1.9 K Node WinNT UICMC20
125,803 Tcp/Ip IdleW 16 S 1.3 K 307.4 M Node WinNT UICMC20
***************************EMAIL DISCLAIMER**************************
This e-mail and any files transmitted with it may be confidential and are
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended recipient or the individual
responsible for delivering the e-mail to the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken
in reliance on it, is strictly prohibited. If you have received this
e-mail
in error, please delete it and notify the sender or contact Health
Information Management (312) 996-3941.
|
