Problem was resolved. But does not address the original errors.

1-31-2003
Initial backup was done and written to disk.

2-1-2003
Data was migrated to a single tape as part of normal migration process.

3-6-2003
Numerous restores were attempted and failed, reason unknown at this time, no
read or write errors, undocumented generic error logged on
Exchange Client and TSM server.
ANR8216W Error sending data on socket 36. Reason 32
>From previous experience this means the session was interrupted from the
client end and breaks the communication connection.
TSM server and exchange restore box were rebooted in an attempt to clear up
a comm issue that seemed to be happening , based on errors.
Restore attempts failed again with the same errors.

3-7-2003
Pushed file to disk in the event that errors were being produced on the
drive or tape and not being reported to TSM.
Restore was attempted after file was pushed to disk, same errors.

3-8-2003
File was migrated to tape as part of normal migration. File now resides on 2
tapes. Restore attempted same error.

3-11-2003
Both volumes were audited, no errors. Q content "volume" damaged=yes  showed
the file was labeled
damaged in the DB, this may be due to the multiple restore failures.
Backed up the DB. Used an undocumented command to set file undamaged.
3 Restores were attempted... again same failure, there were three failures
at different data locations on both tapes. Using the restored file size
as reference. ( 600 mb vol 1, 8.6gb vol 2, 2.2 gb vol 1)

3-12-2003
File was set to undamaged again, Performed another set of audit volumes, set
volumes to readonly, moved data to disk successfully.
Restore was completed successfully. No errors encountered.

3-13-2003
IS was loaded onto sxexrestore. No errors encountered.

NO drive errors were logged during this entire process.

Based on what we have seen, the file was set to damaged after the first
couple of restore failures, it was then move to disk the first time in the
damaged state, each subsequent attempt failed due to the damaged setting.
When the file was set to undamaged, we were seeing what was really
happening, but there were still no errors to give us a better determination.
I am going to attempt the restore from tape again after the mailboxes have
been extracted.


>  -----Original Message-----
> From:         Ochs, Duane
> Sent: Friday, March 07, 2003 9:36 AM
> To:   'ADSM-L@VM. MARIST. EDU (E-mail)'
> Subject:      RE: ANR8216W Error sending data on socket 53.  Reason  32 -
> Update
>
> I attempted a restore after the files were on disk, same results.  I was
> able to restore the Pub.edb individually, but was unable to restore the
> Priv.edb.
>
> While attempting these via command line I get a couple of different
> errors.
>
> Client:
> ACN3035E -- Restore error encountered.
> ANS1314E (RC14) File data currently unavailable on server.
>
> Server error is the same:
> ANR8216W Error sending data on socket 53. Reason 32
>
> Since my message I have found that this restore was requested by my VP. So
> now the pressure is on.  Does anybody know of a way to get these files off
> of the TSM server and back on the box so our exchange group can attempt to
> repair the file and recover the mail boxes ? I know that this can be done
> with ntbackup and a few other programs, but the TDP for exchange does not
> openly allow you to force the files to the server. Any ideas ?
>
>
>
>
>        -----Original Message-----
>       From:   Ochs, Duane
>       Sent:   Thursday, March 06, 2003 5:29 PM
>       To:     ADSM-L@VM. MARIST. EDU (E-mail)
>       Subject:        ANR8216W Error sending data on socket 53.  Reason
> 32
>
>       I reviewed what was on the list. I can see a lot of what it looks
> like and what it might be. But no definitive answers.
>
>       TSM server level 5.1.6.2, aix - 5.1 ml3, 64 bit enabled
>       TDP for exchange 2.2 - NT 4.0 Sp6a Exchange 5.5 sp3
>
>       Attempted to restore a 23 GB IS from Jan 31 2003. I receive this
> error "ANR8216 error sending data on socket 53.  Reason  32 " Now based on
> some of the research I have done it could indicate a client tcpip error or
> similar failure at the client to receive data. I made some config
> adjustments, rebooted the TSM server, rebooted the client and it is still
> producing the same errors.
>
>       For grins I tried the December 2002 IS , also 23 GB it restored
> fine.
>       Tried the February 2003 IS , also 23 GB restored fine. At the moment
> I am moving the volume data to my DISK storage pool in an attempt to
> restore this file.
>
>       I'll let you know what happens.
>
>       Duane Ochs
>       Systems Administration
>       Quad/Graphics Inc.
>       414.566.2375
>
>