How long have you been at 6.3.4.0? I've seen this on slightly older servers 
when Windows 2008 Server clients (and similar era Windows desktop, from what I 
hear) back up their system states. You get huge numbers of small objects, and 
expiration takes a long, long time to process those with no obvious progress.

However, that's supposed to be fixed in 6.3.4.0. I'm wondering if you backed up 
some such clients before upgrading to 6.3.4.0?

Nick


On Aug 9, 2013, at 11:02 AM, "Dury, John C." <JDury AT DUQLIGHT DOT COM> wrote:

> I have an AIX server with TSM 6.3.4.0. Expiration is set to run at 2am and 
> seems to get so far and then hangs. But what's odd is that is also seems to 
> only process some of the nodes but not all. For example, I have it running 
> now and it seems to be stuck:
>       1 Expiration           Processed 462 nodes out of 595 total nodes,
>                               examined 4315 objects, deleting 4271 backup
>                               objects, 0 archive objects, 0 DB backup volumes,
>                               0 recovery plan files; 0 objects have been
>                               retried and 0 errors encountered.
> 
> I looked at previous nights and it ran successfully but only processed 462 
> nodes out of 595 and says it ended successfully. If I cancel the one that is 
> running now, it just hangs and never cancels. The only way to get rid of the 
> process is to halt the server. I have opened a problem with IBM but I thought 
> I would see if any of you have seen this issue.  Any idea why it isn't 
> processing all 595 nodes?