Thanks Del. I will pass it on to my resident Exchange gurus.

        -----Original Message-----
        From:   Del Hoobler [SMTP:hoobler AT US.IBM DOT COM]
        Sent:   Thursday, September 02, 1999 2:03 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: ADSM Connect Agent for MS Exchange question

        Nathan,

        "Waiting for Exchange server......." means that the
        Exchange Agent has made a call to the Exchange Server
        backup API and is waiting for a response...
        ...and it looks like it never gets one!

        There is a Microsoft bug that has to do with this
        and occurs most often on single-CPU machines.

        The Microsoft Exchange bug number is X66942 for Exchange 5.0.
        It was supposed to be part of Exchange Server 5.0 SP3.
        But SP3 is not out for Exchange Server 5.0.

        So..... you will have to order and apply the HOTFIX...

        >>> Any of our customers experiencing this hang, will have to call
        >>> Microsoft Technical support to obtain the fix.  Here are the
        >>> Microsoft Bug numbers that the customers should refer to:
        >>>
        >>>      Bug x5:66198 is for Exchange 5.5  (or in SP1 or later)
        >>>      Bug x5:66942 is for Exchange 5.0  (supposed to be in SP3)
        >>>      Bug x5:66943 is for Exchange 4.0  (only HOTFIX available)

        Contact Microsoft to obtain the HOTFIX for this.


        Also, when you use "/BUFFERS:8,64", it does not mean that
        there are 8 threads being used.  It means that 8 separate
        buffers will be used for data transfer.

        Thanks,

        Del

        ----------------------------------------------------

        Del Hoobler
        IBM ADSM Agent Development
        hoobler AT us.ibm DOT com



        >> Running ADSM Connect Agent for MS Exchange 1.1.0.0A
        >> NT Server 4.0 Sp4 Exchange 5.0
        >> ADSM Server 3.1.2.20 for OS/390 at 2.6
        >>
        >> The majority of our Exchange Servers run with two 400Mhz Xeon
Processors,
        >> however yesterday one of the processors on this server died and
it now
        >> operates on a single processor until we can arrange for parts and
downtime.
        >>
        >> Processor activity however is still quite low about 5-15%.
        >>
        >> However since loosing this processor we have been unable to run a
full
        >> backup.
        >>
        >> The backup starts , does about 3Gb and then hangs up.
        >>
        >> The process excdsmc is still running on the server, however it is
now
        >> getting no CPU time. The session to the ADSM Server is now gone.
        >>
        >> The only hint of an error is the following in the Connect Agent
output log.
        >>
        >>
        >> 53546,(0/2 full)> Wrote  65536 bytes, total: 3509186743
        >> 53547,(0/2 full)> Wrote  65536 bytes, total: 3509252279
        >> 53548,(0/2 full)> Wrote  65536 bytes, total: 3509317815
        >> 53549,(1/2 full)> Wrote  65536 bytes, total: 3509383351
        >> Waiting for Exchange server..................
        >> Waiting for Exchange
        >>
server......................................................................
        >>
............................................................................
        >> ........
        >> Any ideas on how I can get around this while I wait for the new
CPU to
        >> arrive?
        >>
        >> It looks like there's a timeout occuring somewhere, however I'm
surprised to
        >> see the excdsmc process still running (although it's completely
dormant -
        >> doing no paging or cpu time).
        >>
        >> What I found weird also is that although the Exchange Agent is
set to use
        >> buffers 8,64 , perfmon shows only 6 active threads.
        >>
        >> Nathan King
        >> MCSE, IBM ADSM CS