Well, since you have multi-threaded expiration in TSM v6 (basically 1 thread per volume) expiration is alot faster.
That could be an easy way of handling your expiration problems, going to v6, but if your databasevolumes are located on the same arrays, you'll still get lousy performance, just spread over multiple thread instead of one ;) Best Regards Daniel Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -----"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> skrev: ----- Till: ADSM-L@VM.MARIST.EDU Från: "Lee, Gary" Sänt av: "ADSM: Dist Stor Manager" Datum: 02/16/2012 15:32 Ärende: Re: Expiration performance TSM 5.5 (request) Do you have many win 2008 and win 7 clients with client version 6.2.2? For some reason (forget the apar), expiration is very slow with these clients. I am going to 6.3 soon, and hope to solve this with that move. I have a 6.2 server, can't get your script to run, but observation tells me that expirations that run hours on 5.5 run in minutes on 6.2. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, EJ van - SPLXO Sent: Thursday, February 16, 2012 9:02 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Expiration performance TSM 5.5 (request) Hi TSM-ers! I'm struggling with the performance of our expiration process. I can't get it any faster than 100 object/second max. We tried everything, like using more or less database volumes, multiple volumes per filesystem, mirroring, unmirroring, but nothing seems to have any positive effect. We are using SAN attached enterprise class storage (EMC Vmax) with the fastest disks available. I have seen other users with similar (or larger) databases with much higher figures, like more than 1000 objects/sec, so there must be something I can do to achieve this. In 2007 at the Oxford TSM Symposium (http://tsm-symposium.oucs.ox.ac.uk/2007/papers/Dave%20Canan%20-%20Disk% 20Tuning%20and%20TSM.pdf page 25) IBM also stated that 1000 object/sec is possible. I would really like to know from other TSM 5.5 users how their expiration is performing. Could you please let me know by sending me the output from the following two SQL queries, along with the platform you are using: select activity, cast((end_time) as date) as "Date", (examined/cast((end_time-start_time) seconds as decimal(18,13))*3600) "Objects Examined/Hr" from summary where activity='EXPIRATION' and days(end_time)-days(start_time)=0 select capacity_mb as "Capacity MB", pct_utilized as "Percentage in use", cast(capacity_mb*pct_utilized/100 as integer) as "Used MB" from db Thank you VERY much for your help in advance!!!! Kind regards, Eric van Loon KLM Royal Dutch Airlines </pre>********************************************************<br>For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message.<br><br>Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.<br>Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 <br>********************************************************<pre>