Documents Have Disappeared from TSM Before End of Life

[JJeffrey]

Good Morning,

We are running CMOD 8.5.0.6 on a RHEL 5.8 platform with TSM 5.5.1.6. The issue is, and I'm afraid that it IS NOT an isolated instance, documents expired from cache with arsmaint are not in TSM.
In this particular case the documents are in cache for 90 days and TSM for 5 years. The document in question was loaded to CACHE and TSM in September 2013 and expired from CACHE in December 2013 with this command: /opt/ondemand/bin/arsmaint -cdr -g WEBPUB -n 0 -x 0 -u admin.
The user went looking for the document last week and received an error.  We expire by load. When I looked at the logs, the document was not found in TSM. The load information for the object clearly shows that the load to CACHE and TSM was successful but cannot be found in TSM now. CMOD controls expiration of documents in TSM, which has been verified by our storage team.

Has anybody run across this same issue? 

I have an open PMR with IBM and have been running diagnostics for them but answers have not been forthcoming.

[Justin Derrick]

Check the retention policies in TSM.  If you set Life of Data and Indexes to one value, and it's not matched inside TSM, then TSM will delete it on it's own schedule.

There are also different ways to query in TSM, and you can get different results (q content in the admin console vs. a client side query).

Start digging into TSM, and report back what you find in the copygroups and management classes.

-JD.