Re: Retrieve with 5.3 server of data backed up on 5.2.3

2005-02-16 Thread Maria Ilieva
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

Retrieve with 5.3 server of data backed up on 5.2.3

2005-02-15 Thread Maria Ilieva
Hi all, has anyone tried to retrieve files with TSM 5.3, that are backed up with previous TSM server version? I have a problem with files bigger than 5 GB. Every retrieve attempt fails with: ANR1165E Error detected for file in storage pool XXX: Node YYY, Type Archive, File space zzz, fsId 6,

Re: Retrieve with 5.3 server of data backed up on 5.2.3

2005-02-15 Thread Richard Sims
On Feb 15, 2005, at 9:55 AM, Maria Ilieva wrote: ...ANR0548W Retrieve or restore failed for session 41 for node YYY (WinNT) processing file space zzz 6 for file \retrieve.file stored as Archive - data integrity error detected. (SESSION: 41)... Do 'Query Volume ACCess=UNAVailable,DESTroyed' and see

Re: Retrieve with 5.3 server of data backed up on 5.2.3

2005-02-15 Thread Maria Ilieva
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