Since you are investing time in upgrading the client, why not go with
the 5.3.6 on the w2K boxes, and 5.5.1 on the 2003 boxes?  A 5.4 server
will handle 5.5 clients, and you will not have to go back to the 2003
servers when you upgrade your TSM server.

I remember having this problem on some boxes, before I upgraded, where
it was like everything on the server and client thought the backups were
running, but a query of the sessions on the server showed idlew, and no
increase of data flow.  The only thing that resolved our issues was the
client upgrade.  So, since I was having to touch the box anyway, I
started upgrading the clients as I found the problem, and wound up
saving more time than it cost.

See Ya'
Howard


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Huebner,Andy,FORT WORTH,IT
> Sent: Friday, September 26, 2008 10:25 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] TSM Scheduler Hang
> 
> We have started seeing the Scheduler service on Windows hang.
> The backup stops processing, the Schedule stays started, but nothing
> happens.  The fix for now is to stop the scheduler and restart the
> acceptor.  This is only happening on a few of the servers and they do
> not seem to have much in common, they are running different apps.
> 
> Versions:
> Windows 2000 and 2003 (32bit)
> Agent 5.3.2.2 and 5.3.4.8
> TSM 5.4.2.0 (AIX)
> 
> We plan on upgrading the agents to 5.4.2.3 and 5.3.6.0, but this
> process will take some time.
> 
> Andy Huebner
> 
> 
> 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.