bhaven41
ADSM.ORG Member
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.
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.