That's it, alright! That APAR was from ADSM 2.1 closed in July 1997!! I guess the fix is on the "back burner".
David Longo >>> [EMAIL PROTECTED] 03/11/02 11:33AM >>> Yep, it is a design flaw! Apar IC15925 describes this issue. -------------------------------------------------------------------- ERROR DESCRIPTION During an offsite reclamation process; where files are being transfered from disk to tape. ADSM fails to group the files together into transaction groups. Instead the files are processed sequentially. Hence a file will be reclaimed and committed before the next file will be process. ADSM needs to honor the movebatchsize and movesizethresh options in the server options file, so that the files will be grouped together properly for reclimation. As a note, this problem will only be seen where off-site reclamation is occuring from disk to tape. COMMENTS: After taking a very close look at the solution for this APAR, it was determined that the code needed for this performance enhancement is significant because it requires a restructure in the offsite reclamation transaction processing. A requirement can be taken to include this performance improvement in the next release or version. -------------------------------------------------------------------- I have submitted a design request - and actually had a TSM developer call me asking for details on this last September. I haven't heard anything since so I'm thinking they are not persuing it! Please submit your reqests for a design change - perhaps if enough people ask ... Tim Rushforth City of Winnipeg -----Original Message----- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 10:24 AM To: [EMAIL PROTECTED] Subject: Slow Reclamation from disk I have old TSM server 3.7.4.0 on AIX 4.3.3 with 3575-L32 library with C-XL drives. New server is TSM 4.2.1.9 on AIX 4.3.3 ML09 and IBM 3584-L32 library with 8 FC-AL drives. Having the 3584 running for about 6 weeks now, I see what some of the talk about slownes in the last year actually is. On BOTH TSM systems there is slowness in offsite tape reclamation WHEN some of the files being reclaimed are still on the Disk stgpool. When tape reclamation starts, it figures out which tapes to reclaim and where the data is - understand. Then when it actually starts it will copy files that are STILL in disk stgpool first before files that are only on tape - makes sense. Then move to files that are only on tape. However, when it is copying files from disk it is MUCH slower than when copying from tape - I would say 10 times slower. But when doing a MIGRATION disk to tape or BACKUP STGPOOL fromdisk to tape on either system, it's like going from idle to 4th gear! This slownes can happen on thses system when there is NO OTHER ACTIVITY but this single reclamation. Having two different systems to compare at the same time seems to indicate that this is NOT a disk problem or a tape problem (except that the 3584 may not handle it quite as well). Also our old system tended to have disk pool emptier when reclaimation started and this wasn't really noticed on that system until I started paying close attention. I again point out that my 3584 really smokes when doing everything else BUT reclamation from disk to tape. So does the 3575 - relatively speaking. (My 3584 library is library F/W 2360 and drives are 18N2 as delivered, I don't think this is problem but included for completeness). It seems that this is some inherent Tivoli design flaw/feature in the RECLAMATION process. Anyone with detail knowledge of Reclamation can provide some insite? Andy Raibeck? Thanks, David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax: 321.434.5525 [EMAIL PROTECTED] "MMS <health-first.org>" made the following annotations on 03/11/02 11:37:16 ---------------------------------------------------------------------------- -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ============================================================================ == "MMS <health-first.org>" made the following annotations on 03/11/02 12:04:18 ------------------------------------------------------------------------------ This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==============================================================================
