ADSM-L

Re: Exchange failure backing up InfoStore

1999-09-15 15:27:05
Subject: Re: Exchange failure backing up InfoStore
From: Del Hoobler <hoobler AT US.IBM DOT COM>
Date: Wed, 15 Sep 1999 15:27:05 -0400
Seth,

You need to take a look at the ADSM Server activity
log to find out what it thinks happened.

The symptoms indicate that the ADSM server was busy
but was processing the data.  Then, the final send
of data received a TCP/IP connection failure which
indicates that the session was cut off while waiting
for a response from the ADSM Server.

Was there a tape mount request?
Was there any tape I/O related to this backup?
(like end of volume processing...)

The ADSM Server activity log is key to finding
out what happened.  If the ADSM Server didn't terminate
the connection for some reason, take a look at the
network (and Windows NT) to find out why the TCP/IP
communication was severed.

Thanks,

Del

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

> I am trying to backup an Exchange Information Store to ADSM 3.1.2.40 for NT.
> Each time I run the backup I get the following message at varying points.
>
>           Database : Information Store
>        Backup Type : Full
>
> Logging on to the ADSM server...
>
>  1099,(1/2 full)> Wrote  65536 bytes, total: 72020163
> Waiting for ADSM server...
>  2373,(1/2 full)> Wrote  65536 bytes, total: 155513027
> Waiting for ADSM server...
>  3653,(1/2 full)> Wrote  65536 bytes, total: 239399107
> Waiting for ADSM server...
>  4942,(1/2 full)> Wrote  65536 bytes, total: 323875011
> Waiting for ADSM server...
>  6232,(1/2 full)> Wrote  65536 bytes, total: 408416451
> Waiting for ADSM server...
>  7493,(1/2 full)> Wrote  65536 bytes, total: 491057347
> Waiting for ADSM server....
>
> Backup error encountered.
> ANS1017E (RC-50)  Session rejected: TCP/IP connection failure
>
> After the TCP/IP failure I have to stop Exchange before I can try again. The
> IS is about 11 GB. I have increased the COMMTIMEOUT to 36000 and turned off
> compression on the client. Any suggestions?
> Seth Forgosh