On Dec 14, 2007, at 10:55 AM, Fred Johanson wrote:
This sounds like PMR#64846-122, which is still open after months of
work. The last thing in the traces we ran is a TCPFLUSH. After that
things hang forever.
That reminds me of the trivial but helpful diagnostic of running the
'netstat' comma
This sounds like PMR#64846-122, which is still open after months of
work. The last thing in the traces we ran is a TCPFLUSH. After that
things hang forever.
Fred Johanson
TSM Administrator
University of Chicago
773-702-8464
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAI
I would look at your network connection first. Based on the throughput
stats, I'm guessing you have a nic/switch mismatch between either the
speed or duplex setting.
Steve Schaub
Systems Engineer, WNI
BlueCross BlueShield of Tennessee
423-535-6574 (desk)
423-785-7347 (cell)
***public***
-Or
I don't see anything in the activity log. The backups are going straight
to diskpools and the backups are single threaded. I did add disk space
to my diskpool this week in case that was the issue. Looking at my
diskvols, data doesn't seem to be striped across all disk evenly, would
that be that pro
Did you examine the TSM Server activity log closely?
Was there a problem where a tape did not get mounted in time?
How many "stripes" are you using for the backup?
If you are using multiple stripes and one of those stripes
is waiting for the TSM server to mount a tape, it can cause this.
I have see
You have received a secure message from Ben Bullock entitled, "RE: [ADSM-L] sql
tdp hang issue".
You may view the message (before 06/21/2008) at the following web address:
https://mail.bcidaho.com:443/messenger/msg?x=d-42733-qh6GFAGG8617
---
