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
Open Systems Storage Management
*  (210) 913-5755
* Pager: 753-5755
* E-mail: nathan.king AT usaa DOT com

The opinions herein are mine and almost certainly do not reflect those of my
employer.