Matt,

You should really look closely at the Exchange Server
side of this.  Look in the excdsm.log file (or whatever
you named it) to find out why the backups are failing...
...if they really are failing that is.

If this is a scheduled event, you may want to check the
script that starts the backup.  It could be that this is
merely the client session that started the Exchange backup
scheduled event and not the session actually running the
backup.  For example, if the scheduled event is a
COMMAND type schedule that kicks off a batch file
that contains the commands to run the backups then
that session won't end until the entire backup is complete...
(that is, until the batch file runs to completion)
...unless you put the word "start" in front of the
"excdsmc" command so that the batch file simply starts
the command and returns.  For example:

Instead of this:

   excdsmc /backup:is,full  >> excsched.log

Do this:

   start excdsmc /backup:is,full  >> excsched.log

But...  This is only an educated guess on what's going on
since I have seen this a number of times before.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com


"Long, Matt" <Matt.Long AT MARRIOTT DOT COM>@VM.MARIST.EDU> on 02/07/2000 
05:33:58
PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Exchange backup failures



To All,

Has anyone seen this error before. Its causing one of our Exchange backups
to fail everyday.

02/07/00   12:27:05      ANR0481W Session 140002 for node nodename (WinNT)

                          terminated - client did not respond within 3600
seconds.

Matt Long
Systems Administration
Marriott International