> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 
> On Behalf Of Richard Sims
> Sent: dinsdag 8 november 2005 13:21
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Backup hangs the Windows 2000 server client
> 
> On Nov 8, 2005, at 3:09 AM, Alexander Verkooijen wrote:
> 
> > We also have a number of Windows 2000 clients
> > (5.3.2.0) that seem to hang the entire system
> > during a backup. The client has to be rebooted
> > to get it working again. ...
> 
> The poster of the original question had a TSM server which was
> utilizing default timeout values - which are far too low for real
> world conditions, where clients have to spend a lot of time rummaging
> around in file systems seeking backup candidates before they next
> interact with the server. The server may deem such sessions hopeless
> and terminate them from its end, where sometimes the client "doesn't
> get the message" that the session was cut off.
> 
> In all "hang" situations, you need to dig in and extract the details:
> most "hang" situations are not hangs at all, but peer situations
> where one side is busy and the other is waiting for it. Look for ANR
> messages in your TSM server activity log, any OS or dsmerror.log

You are right. I forgot to include a message the user found
in his OS log files (or whatever they are called under Windows).
Please allow me to correct my mistake.

This is the error the user found:

Event Type:        Error
Event Source:        tsmlvsa
Event Category:        None
Event ID:        29
Date:                3-11-2005
Time:                4:00:09
User:                N/A
Computer:        BGS-242-20
Description:
Encountered exception [C0000005] during copy-on-write operation.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data:
0000:  00 00 00 00 02 00 58 00   ......X.
0008:  00 00 00 00 1d 00 07 c0   ......À
0010:  00 00 00 00 00 00 00 00   ........
0018:  00 00 00 00 00 00 00 00   ........
0020:  00 00 00 00 00 00 00 00   ........

The APAR I referred to describes the same symptons
which led me to the conclusion that I was suffering from
the LVSA problem the APAR describes.

Regards,

Alexander