Re: expire inventory seems to be hanging and not processing all nodes
-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 We've been running v6.3.4.0 for a few weeks now. -I saw a similar behavior on my 6.3.3.100 on Windows earlier this week. - -Expiration appeared to be stuck for a couple of hours having processed only 10 -or 15 nodes of 200. - -Do you have a duration specified to limit time? That might explain your 462 of -595. - -I had also tried to cancel, and also did the halt to clear the process. - -Upon restarting, then a new expire, it again appeared to stall, but in time -picked up and cruised through without issue. - -All expiration since that day has run fine, in "normal" behavior and timespan. I do not have duration limit on the process. I looked at a previous night and it ran in 90 minutes or less. The current one has been running for a few hours and is still hung at 462 out of 595 nodes and the number of objects hasn't changed. From: Dury, John C. Sent: Friday, August 09, 2013 12:03 PM To: ADSM-L (ADSM-L@VM.MARIST.EDU) Subject: expire inventory seems to be hanging and not processing all nodes 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?
Re: expire inventory seems to be hanging and not processing all nodes
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." 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?
Re: expire inventory seems to be hanging and not processing all nodes
I saw a similar behavior on my 6.3.3.100 on Windows earlier this week. Expiration appeared to be stuck for a couple of hours having processed only 10 or 15 nodes of 200. Do you have a duration specified to limit time? That might explain your 462 of 595. I had also tried to cancel, and also did the halt to clear the process. Upon restarting, then a new expire, it again appeared to stall, but in time picked up and cruised through without issue. All expiration since that day has run fine, in "normal" behavior and timespan. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dury, John C. Sent: Friday, August 09, 2013 11:03 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] expire inventory seems to be hanging and not processing all nodes 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? [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
expire inventory seems to be hanging and not processing all nodes
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?
