Andy,
I am having issues backing up WFSB03. It has Journaling on d$ . I
have been keeping close watch on the throughput but it looks like it is
slowing down. Is there a way to find out if the session is still alive?
The 'IdleW ' state concerns me as this is the 3 time I tried to get this
node backed up properly.
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 03:34:11.000000
Bytes sent/second: 90192.2094000466889
Bytes received/second: 2453.0828729281767
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 03:34:43.000000
Bytes sent/second: 89968.1911821780641
Bytes received/second: 2446.9993014049522
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 03:39:53.000000
Bytes sent/second: 87854.2738573485939
Bytes received/second: 2389.5944819222314
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 03:58:21.000000
Bytes sent/second: 81047.8967205090553
Bytes received/second: 2204.7728130899937
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 04:04:37.000000
Bytes sent/second: 78971.6911494174558
Bytes received/second: 2148.3951761259112
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 04:09:10.000000
Bytes sent/second: 77529.6740468227424
Bytes received/second: 2109.2382608695652
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 04:11:50.000000
Bytes sent/second: 76708.7549305095962
Bytes received/second: 2086.9471872931833
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 04:18:32.000000
Bytes sent/second: 74720.9205131511088
Bytes received/second: 2032.9682826199071
Session: 1802
Client: WFSB03
State: IdleW
Elapsed Time: 0 04:39:40.000000
Bytes sent/second: 69074.8576281287246
Bytes received/second: 1879.6541120381406
Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976
Andy Huebner
<Andy.Huebner@ALC
ONLABS.COM> To
Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU
Dist Stor cc
Manager"
<[email protected] Subject
.EDU> Re: [ADSM-L] questions on Sessions
09/21/2007 02:34
PM
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
It looks like TSM is scanning the node. The server has sent 1.1G. I do
not remember seeing more than one session until the node starts sending
data.
Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Avy Wong
Sent: Friday, September 21, 2007 1:12 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] questions on Sessions
Hello.
Can you tell me that it is always true everytime you kick off a
backup be it from the server side or client side that it always shows 2
sessons of the same node on the Command Line Administrative Interface? I
noticed that WFSB03 does not have two sessions and thoughput is slow or
am
I too impatient? I have kicked off a backup from the server side
calling
WFSB03 to run the backup now and I only see one session. Any explanation
for the single session?
Thanks.
tsm: TSMEARTH>q sess
Sess Comm. Sess Wait Bytes Bytes Sess
Platform Client Name
Number Method State Time Sent Recvd Type
------ ------ ------ ------ ------- -------
-----
-------- --------------------
6 Tcp/Ip IdleW 2.2 M 257 1.5 M
Serv-
AIX-RS/- TSMSKY
er
6000
8 Tcp/Ip Run 0 S 1.4 M 257
Serv-
AIX-RS/- TSMSKY
er
6000
194 Tcp/Ip IdleW 20.0 H 469 341 Node
WinNT MAIL1TDP
214 Tcp/Ip Run 0 S 42.5 K 1.1 T Node
TDP Dom- MAIL1TDP
ino
1,802 Tcp/Ip IdleW 0 S 1.1 G 30.1 M Node
WinNT WFSB03
2,178 Tcp/Ip Run 0 S 60.0 K 519
Admin
WinNT WONGAV
Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976
************************************************************************
**************************
The information contained in this message may be privileged and
confidential and
protected from disclosure. If the reader of this message is not the
intended recipient, or
an employee or agent responsible for delivering this message to the
intended recipient,
you are hereby notified that any dissemination, distribution, or copy of
this
communication is strictly prohibited. If you have received this
communication in error,
please notify us immediately by replying to the message and deleting it
from your
computer.
************************************************************************
**************************
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using,
copying or distributing the information in this e-mail or its attachments.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message and any
attachments.
Thank you.
**************************************************************************************************
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended
recipient, or
an employee or agent responsible for delivering this message to the intended
recipient,
you are hereby notified that any dissemination, distribution, or copy of this
communication is strictly prohibited. If you have received this communication
in error,
please notify us immediately by replying to the message and deleting it from
your
computer.
**************************************************************************************************
|
