We went round-and-round with Tivoli on this issue. They say it's working as designed. Here's what's happening...
When the location of a file is on DISK which is RANDOM access, then TSM processes the files ONE AT A TIME instead of batching them together like on SEQuential media. We first discovered this with the DIRMC...our policy put the directories into a DISK storage pool and then copied them to offsite each day. Then the reclamation ran forever. Tivoli says that RANDOM DISK is processed 1 file at a time and they have no plans to change this. SO you can imaging how many 1 at a times there are reclaiming your DIRMC pool. Now we configure up with a first-level DISK pool that we migrate for a FILE devclass. The FILE is a SEQuential media and reclamation runs OK. So, if you can migrate the data before you start the reclamation you should get better response times. HTH, Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Sparrman Sent: Monday, March 11, 2002 11:26 AM To: [EMAIL PROTECTED] Subject: Re: Slow Reclamation from disk Hi How is your diskpool configured? Is it placed locally on the machine, or is it SAN attached? Best Regards Daniel Sparrman ----------------------------------- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 David Longo <David.Longo@HEALTH To: [EMAIL PROTECTED] -FIRST.ORG> cc: Sent by: "ADSM: Subject: Slow Reclamation from disk Dist Stor Manager" <[EMAIL PROTECTED] DU> 2002-03-11 17:23 Please respond to "ADSM: Dist Stor Manager" 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. ============================================================================ ==