Stephanie,

In view of these fact I have to agree with the previous post that the client
is probably busy looking at a mass of directories and or files.

As he suggested the only way I know of overcoming this is to increase the
idletimeout parameter.

You mention that these are Notes servers. I've never used the Notes Connect
Agent, but it may be able to give better performance in this instance.
Perhaps someone in the forum can comment on this?

You may want to consider downloading a trial version and testing it on a
non-production notes server (if you have one).

Nathan
        -----Original Message-----
        From:   Stephanie.CANON AT CIGMA.ASSO DOT FR
[SMTP:Stephanie.CANON AT CIGMA.ASSO DOT FR]
        Sent:   Thursday, October 14, 1999 7:00 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Réf. : Re: ADSM scheduled backup hangs on the second
partition


        The NT servers are Notes servers. The D drive is where the Notes
databases are.
        We stop the Notes server, then run the backup using the ADSM client.
        We have actually 4 Notes servers, and the problem occurs only on 3
of them.

        In the dsmerror.log, there is no message, just nothing, and on the
MVS server,
        the message is :

        ANR0482W Session 1359 for node GRI00 (WinNT) terminated - idle for
more than 60
        minutes.

        In the dsmsched.log, nothing. It's just like the client was lost and
did
        nothing.

        Stéphanie



         << File: ATT99947.txt >>