Richard, "The only explanation I can think of for this would be the influence of the EXPINterval server option, if that hasn't been deactivated; but I'd expect that you'd have seen evidence in the Activity Log."
I just verified that ExpInterval is set to zero. I was pretty sure that it was. We've been controlling the expiration via cron scripts since ADSM 2 was first installed. And in reference to Remco's message, we check for failed processes daily. There were no failed reclamations at the end of the last maintenance cycle, so there was nothing lingering for TSM to resume. I think Guillaume might have figured it out. Let's say we keep five versions of a file. If, during the night, the system picks up a sixth version, does the oldest version scroll off immediately? Or does it wait for reclamation? If immediately, that is almost certainly what happened. But what is odd is that I've never noticed that occurrence before despite administering the system for the last seven years! Thanks. Tab
