Sp4 is released
 
Full packeage (130 MB)
http://download.microsoft.com/download/e/6/a/e6a04295-d2a8-40d0-a0c5-241bfec
d095e/w2ksp4_en.exe
 
 
Express Install (600K)
http://download.microsoft.com/download/b/1/a/b1a2a4df-cc8e-454b-ad9f-378143d
77aeb/sp4express_en.exe


-----Original Message-----
From: Henrik Wahlstedt [mailto:shwl AT STATOIL DOT COM] 
Sent: vrijdag 27 juni 2003 9:29
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: backup systemobject hanging on win2k


Hello Joe and others,

The problem might be that your w2k client doesnt 'tell' that the scheduled
backup is complete when it contacts your TSM server, instead it starts
another scheduled backup i.e. it loops. Probably, you cant locally backup
system object either, client will crash.

I dont recall the name of the security fix from MS that caused this problem,
but we tried to uninstall the fix but that didnt solve the problem. In my
case, I´m busy at the moment upgrading 250+ w2k servers to v.5.1.6.0.

And the best part is... all security hotfixes will be in SP4 which will be
released pretty soon. :D Andy -Do you this as a problem?

Also, see previous threads this month about this.


//Henrik




 

                    Joe Howell

                    <jhowell_tsm@        To:     ADSM-L AT VM.MARIST DOT EDU

                    YAHOO.COM>           cc:     (bcc: Henrik Wahlstedt)

                    Sent by:             Subject:     backup systemobject
hanging on win2k                         
                    "ADSM: Dist

                    Stor Manager"

                    <ADSM-L AT VM DOT MA

                    RIST.EDU>

 

 

                    2003-06-26

                    15:25

                    Please

                    respond to

                    "ADSM: Dist

                    Stor Manager"

 

 





I'm running TSM 5.1.5 on OS/390 and backing up Win2K servers running the
5.1.5 client.  I issue a "define clientaction nodename action=command
object='dsmc backup systemobject'" from the server to each of my clients at
the beginning of my backup cycle, followed by a "define clientaction
nodename action=incremental" command.  The first command gets scheduled
right away, but it appears that in many cases the scheduled command takes
hours to finish and get out of the way so that the incremental backup can
begin.  All I see in the server log is that the session times out and that
eventually it reconnects and the schedule completes.  I don't see any errors
in the client log.  Any ideas on what might be going on?  I do see that the
schedule prompter keeps bugging the client to start the incremental; is it
possible that this is causing a problem for the client scheduler?


Joe Howell
Shelter Insurance Companies
Columbia, MO

---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!





-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message. Thank you.