ADSM-L

Re: Resolved: URGENT!! TSM client schedules not running

2003-08-14 12:00:51
Subject: Re: Resolved: URGENT!! TSM client schedules not running
From: "Coats, Jack" <Jack.Coats AT BANKSTERLING DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 14 Aug 2003 11:02:30 -0500
It soudns like if you do a 'netstat -e' from the command line, this could
be the issue if you see lots of errors under the recieve column.

Now how to change it is the next question :)

-----Original Message-----
From: Debi Randolph [mailto:Debra.Randolph AT FBOL DOT COM]
Sent: Thursday, August 14, 2003 10:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Resolved: URGENT!! TSM client schedules not running


Can anyone translate this to the Windows world?



[snip]
                      08/14/2003 10:04

                      AM

                      Please respond to

                      "ADSM: Dist Stor

                      Manager"



My problem was also with Prompted nodes only.  Polling nodes ran ok as
did croned backups.

The tcp setting was the size of the Receive Pool Buffer.  IBM gave me
this query to determine if there was a problem:
  (echo "----";date; netstat -v ent1 | grep "Receive Pool Buffer" )

The "No Receive Pool Buffer Errors" line should report zero.  They had
me set the "Receive Pool Buffer Size" up to 2048 (AIX 5.1).
Unfortunately, I don't remember the command to do that.

David

>>> guillaume.gilbert AT DESJARDINS DOT COM 08/14/03 10:29AM >>>
Ok you guys had to start talking about this and now it has happened to
me. Nearly all my servers in prompt mode didn't take a backup last
night. Nothing in  the activity
log and nothing in the dsmsched.logs. I'm running server 5.1.6.4 on AIX
5.1 and clients range from 4.1.2.12 to 5.1.5.15, all Windows (NT and
2k). Most of these servers
had the MS patch installed for the blaster virus yesterday. Is this
just a coincidence??. I know its not a network problem because all my
UNIX clients where running
backups all night and those are not scheduled by TSM but by crontabs.

So David, what was the tcpip settings you had to change?

Thanks

Guillaume Gilbert
[snip]
____________________________________________________________

When I had the problem, I did open a PMR and they finally tracked my
problem down to a tcp read buffer problem.  They had me adjust the tcp
values and the problem has not reoccurred.

David
[snip]

<Prev in Thread] Current Thread [Next in Thread>