I wouldn't say expiration running over 24 hours a cause for alarm per say.
I have seen expiration running over 10 days. This occurred when TSM server
was upgraded to address expiration issue with Windows system objects. Few
years back.
That being said, I would examine past actlog to see i
To Whom It May Concern:
Expiration ran over 24 hours yesterday. I cancelled it when the DB
backup job started. We recently migrated 30-40 volumes from an old
sequential pool that became went into pending. About 30 volumes passed
the re-use delay period and went to scratch 2 days ago. I was wonderi
