Expiration in TSM 6.1

[bhaven41]

Hi,

I am running TSM Server 6.1.2.0 on AIX 5.3 with FILE volumes and De-Dup is active.
Running Identify process daily for some duration.

Since last couple of days my expiration is hanging.
It runs for some time, updates the "query process" output with x number of objects deleted once or twice, and after that those figures never change.

I can see that Active Log utilization keeps increasing.
I keep it running for 5 hrs and still no update in those figures.

So I assume it is hung and when try to cancel it, it shows that cancel is pending however after 2 hrs also it does not get cancelled.

I have to restart TSM server to cancel it.

Is anybody else experiencing this kind of situation?
Does it have to do with De-Dup? Does it takes hours just to find out what to expire because of de-dup?

Appreciate any help in this case.

 

[keteran]

I have the same problem, did you ever determine a solution?

 

[bhaven41]

Yes, IBM has provided a diag sever which is working fine at the moment.

 

[adsm04]

Expiration issue on TSM 6.1.2

Hi I'm facing the same issue for expiration on TSM 6.1.2
Expiration runs for a long time with 0 objects inspected. If i cancel it, it hangs without cancelling. The only way is to halt the TSM server. Again after restart same issue. Any solution for this pls. Thanks in advance guys!!

 

[bhaven41]

upgdare or patch the TSM sever

 

[adsm04]

Any other interim solution other than upgrade......i wont be in a position to upgrade for nex 2 to 3 weeks!!

 

[bhaven41]

You may try disabling de-dup(do not run identify process).
I do not remember exactly - may be this helped me till I patched my server.

 

[Nicke]

FYI,
With TSM Server version 6.1.3.2 and active de-duplication running the expiration process works as it should.

I've not encountered this case before and it sounds like a bug in 6.1.2 ..

Regards,
nicke