George,

What version of TSM are you running.  You said 5.3.?

Have you recently upgraded your TSM server?  


We recently ran into a problem with expiration.  We were on version
5.3.1.0.
TSM support recommended we upgrade to 5.3.4.0.  

Snippet from TSM support 
APAR IC46523 about similar behavior after a volume has been deleted -
this APAR is fixed at TSM Server v5.3.2.0 or higher (we recommend the
latest maintenance level). 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Hughes, George
Sent: Friday, November 03, 2006 8:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Inventory expiration suddenly grew by order of magnitude.

To Whom It May Concern:

Starting two days ago our daily inventory expiration job began ran over
24 hours. Previously it ran for 2-4 hours. The number of objects
processed was anywhere from 30,000-700,000 but usually was in the
250,000 range. Now it is processing 4,000,000 objects in about 24 hours
and I have cancelled the job to allow the DB backup to run unfettered.

Recently I migrated data from an obsolete pool to our secondary
sequential pool. I had about 40 tapes in pending which all reached their
re-use delay period about 2-3 days ago. About 10 of these LTO2 tapes
were full and the remainders were mostly empty. Do pending tapes moving
to scratch cause all contained objects previously tracked in the DB to
be expired?

The environment:
TSM Server: AIX 5.2 running TSM 5.3.
DB: 105 GB which is 57% used.



George Hughes

Senior UNIX Engineer

Children's National Medical Center

12211 Plum Orchard Dr.

Silver Spring, MD 20904

(301) 572-3693


Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.