Carefully scan your activity log for messages between the time the reclamation started and ended, especially warning and error messages. Look specifically for any ANR9999D messages. Contact IBM technical support for further assistance and report your findings to them (they should ask to see your activity log from the timeframe I mentioned).
Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 12/10/2004 08:28:05: > Does this look familiar to anyone ? > > After upgrading the TSM server (WIN2K,SP4) from 5.2.2.2 to 5.2.3.0 > the reclamation for our COPYPOOL_COLL reports > unreadable files, sometimes even before it has accessed any tapes > (see log message below). > > 203 Space Reclamation Offsite Volume(s) (storage pool COPYPOOL_COLL), > Moved Files: 2336025, Moved Bytes: > 489,968,253,- > 125, Unreadable Files: 107, > Unreadable Bytes: 0. > Current Physical File (bytes): 24,781,030 > Curre- > nt input volume: BP5079L2. > Current output > volume: BP5013L2. > > Auditing the corresponding tapes and the corresponding disc volume > did not result in any errors. As I am rather unhappy > with the current situation all input/advise and tips are welcome. > > Best regards, > > Jacob Post, [EMAIL PROTECTED]
