>From IBM support answered that our case is APAR IC44818: TSM SERVER MAY
CRASH OR INVALIDLY ISSUE DAMAGED FILE ERRORS WHEN READING DATA OFF OF A
SEQUENTIAL VOLUME
This bug will be fixed in 5.3.0.2

Till now the only workaround we found is to restore data lanfree. But
this is not tested for Windows clients.

Maria Ilieva

-----Original Message-----
From: Richard Sims [mailto:rbs AT bu DOT edu] 
Sent: Wednesday, February 16, 2005 4:01 PM
To: Maria Ilieva
Subject: Re: Retrieve with 5.3 server of data backed up on 5.2.3

Maria -

Okay, then, with any Destroyed volume resolved, that cause should be out
of the way. The Damaged status is troubling, though. We haven't heard
from any 5.3 users of such a problem, and I don't see any current,
closed APARs with such problem indications, so the cause is unclear.
Your open call to IBM may find the reason.

A slim cause that might have some bearing may be a downlevel device
driver involved in tape drive access, which may be erroneously causing
good volumes to look bad. A search back in your Activity Log may turn up
the instance where the volume came to be this way, with maybe some clue
as to what incited it. Beyond that, IBM will have to advise.

     Richard

On Feb 16, 2005, at 2:48 AM, Maria Ilieva wrote:

>> Do 'Query Volume ACCess=UNAVailable,DESTroyed' and see if that 
>> classic cause fits this case. See that msg in ADSM QuickFacts for 
>> what we have collectively seen for circumstances. Look in the 
>> Activity Log for the volname involved and if not Destroyed, do 'Query
CONtent VolName ...
>> DAmaged=Yes' and see if any Damaged files on it.
>
>>   Richard Sims
>
>
> There are no destroyed tapes, except one, that I tried to restore from

> copypool volume. So its access is normal But  'Query CONtent VolName 
> XXX DAmaged=Yes' shows for damaged all files that I tried to retrieve.
> I think the problem is not bad volumes!
> I run retrieve on different clients, for randomly chosed files. So 
> retrieved data are spanned on different volumes.
>
> Every time the retrive fails for files bigger than 5 GB and the
summary
> always shows "Total number of   bytes transferred:  1.33 GB"
>
>  ANE4956I (Session: 4870, Node: NODE1)  Total number of   objects
> retrieved:        1(SESSION: 4870)
>  ANE4959I (Session: 4870, Node: NODE1)  Total number of   objects
> failed:           1(SESSION: 4870)
>  ANE4961I (Session: 4870, Node: NODE1)  Total number of   bytes
> transferred:  1.33 GB(SESSION: 4870)
>  ANE4963I (Session: 4870, Node:NODE1)  Data transfer   time:
> 18.93 sec(SESSION: 4870)
>  ANE4966I (Session: 4870, Node: NODE1)  Network data   transfer rate:
> 73,826.07 KB/sec(SESSION: 4870)
>  ANE4967I (Session: 4870, Node: NODE1)  Aggregate data   transfer
rate:
> 8,651.30 KB/sec(SESSION: 4870)
>  ANE4964I (Session: 4870, Node: NODE1)  Elapsed   processing time:
> 00:02:41(SESSION: 4870)
>
>
> I looked at ADSM QuickFacts for solution and tried restore volume from

> copy pool, to move data, audit volume ..... but nothing helped.
>
>
> Maria Ilieva