My experience (which confounded IBM) is the expires would never end (let it
run for over 9-days) even when picking a single node to expire. I was
restarting the TSM server on a daily basis, it not multiple times a day -
especially when I was going the expires 1-by-1 to determine which nodes
were c
Thanks. I think the reason why EXPIRE INVENTORY without NODES only seems
to expire a small amount of nodes is that it tries to continue where it
left the last time it stopped – if you happen to normally run expire
with DURATION= limitation. If TSM cancels the expire process
after duration is exceed
Here is the 6.3.6.000 expiration problem APAR description:
IT17642: SLOW EXPIRATION AFTER UPGRADE TO 6.3.6.000 SERVER
APAR status - OPEN -
*Error description*
After upgrading the server to 6.3.6.000 (or higher) and 7.1.3(or higher)
expiration might "hang" on a node while expiring backup data onl
Not sure. We have always used "expire inventory resource=8" with no issues
until 6.3.6.000
Since the APAR info is behind IBM's support wall (don't get me started on
the inability to get firmware updates for my IBM TS3500 library from IBM),
I don't know if I can post it here. Hopefully someone fr
Thanks Zoltan, – I somehow missed your earlier posting about this topic.
I'll try to get my hands on the IT17642 article (why on earth does IBM
show it only to "authorized" users? I hate this vendor BS.).
But in addition to slowness, it seems that EXPIRE INVENTORY NODE=* at
least attempts to exp
Henrik,
If you check recent posts here, you will see there is a major issue with
6.3.6.000 server and expirations. I have been fighting it since I upgrade
one server. IBM has a hotfix to address it or you can simply upgrade to
7.1.6, which is what I did. You must contact IBM support for it. The
On Thursday 13 August 2015 14:10:16 you wrote:
> Just went from v6.3.5.100 to v7.1.1.300. The procedure went smoothly,
> but so far I'm not impressed with the client backup - slow to start, slow
> to run. I'd hate to think that the only solution for the performance is a
> bit of sleight of hand to
Just went from v6.3.5.100 to v7.1.1.300. The procedure went smoothly,
but so far I'm not impressed with the client backup - slow to start, slow
to run. I'd hate to think that the only solution for the performance is a bit
of sleight of hand to reconstruct the tablespace.
Database is only ~350G wi
If you cancel an expiration, does it not log every transaction, so that
when you cancel, it effectively does a rollback on all the entries in the
database? That might take some time as well...
On Wed, May 6, 2015 at 4:31 PM, Vandeventer, Harold [OITS] <
harold.vandeven...@ks.gov> wrote:
> I'm run
-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 ob
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 obv
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 di
> Looks like the response is that the fix will be in 6.1.6, due sometime
next year.
Are you kidding on this? a "bug" introduced in a patch is going to
generate annoying error messages every day for the next 5+ months? My
monitoring system (TSMManager) send me error emails for each message and
> Any way to suppress these harmless/annoying messages?
Unfortunately, no.
> Since they are "harmless", am I right in guessing someone forgot to turn
> off some debugging code/messages?
No, but the effect is the same.
> While I don't mind opening up a PMR, I would assume there is going to be
a
Mark,
Any way to suppress these harmless/annoying messages?
Since they are "harmless", am I right in guessing someone forgot to turn
off some debugging code/messages?
While I don't mind opening up a PMR, I would assume there is going to be a
quick update (6.1.5.11?) to address it?
Zoltan Fo
Thank you for the info.
Just for the ha-ha's, I ran another expire and it didn't generate any
errors. However, I found it interesting that it still found something to
delete considering there weren't any backups run and there was only about
10-minutes between runs. I guess if the expiration p
> 7/28/2011 10:20:14 AM ANRD_3916334743 ComputeHashValue
(tbcache.c:4313) Thread<91>: Table Group.Leaders, Column 4 of type 0 not
valid for hashKey.
This is a known problem, fixed in internal defect 73872. It is not related
to the Win2K8 system state cleanup problem. All indications are that
be ok
and not run daily.
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu]on Behalf Of
Grigori Solonovitch
Sent: Friday, July 02, 2010 5:25 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: expire inventory process
There is dependency between reclamation and expiry p
an.svensson
Supported Platform for CPU2TSM::
http://www.cristie.se/cpu2tsm-supported-platforms
Från: Sheppard, Sam [sshepp...@sddpc.org]
Skickat: den 5 juli 2010 20:20
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: Expire Inventory Hangs?
I have an open apar on a simila
-L@VM.MARIST.EDU
Ämne: Re: Expire Inventory Hangs?
On Jul 5, 2010, at 5:29 AM, Christian Svensson wrote:
> Hi,
> I have a TSM Server 6.1.3.4 running on a Windows Server 2008 R2.
> When I run Expire Inventory on my server it seams to hang on a unique node
> and I think I have found the
e.se
Skype: cristie.christian.svensson
Supported Platform for CPU2TSM::
http://www.cristie.se/cpu2tsm-supported-platforms
Från: Nick Laflamme [dplafla...@gmail.com]
Skickat: den 5 juli 2010 15:22
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: Expire Inventory Hangs?
On Jul 5, 2010,
On Jul 5, 2010, at 5:29 AM, Christian Svensson wrote:
> Hi,
> I have a TSM Server 6.1.3.4 running on a Windows Server 2008 R2.
> When I run Expire Inventory on my server it seams to hang on a unique node
> and I think I have found the exact node it hangs on.
> My question is.
> How can I solve th
run daily.
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu]on Behalf Of
Grigori Solonovitch
Sent: Friday, July 02, 2010 5:25 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: expire inventory process
There is dependency between reclamation and expiry process. Y
just on weekends, would running expire inventory just
> prior be ok
> and not run daily.
>
> Tim
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu]on Behalf Of
> Grigori Solonovitch
> Sent: Friday, July 02, 2010 5:25 PM
> To: ADSM
: Re: expire inventory process
There is dependency between reclamation and expiry process. You have to run
expiry daily to have daily reclamation. I have scheduled reclamation 3 times
per day at time suitable for automatic reclamation.
From: ADSM: Dist
There is dependency between reclamation and expiry process. You have to run
expiry daily to have daily reclamation. I have scheduled reclamation 3 times
per day at time suitable for automatic reclamation.
From: ADSM: Dist Stor Manager [ads...@vm.marist.ed
Thank you to those you replied for quick turnaround information. I
replied to not necessary in the order who replied first :-) But you know
who you are.
Actually I meant to say I would like to expire per node name not
alphabetical. We performed a manual backup delete and wanted to see the
Hi Sung,
Expiring inventory by node seems to be one goal fro the next TSM
release, see this presentation from Dave Cannon :
http://tsm-symposium.oucs.ox.ac.uk/2007/papers/Dave%20Cannon%20-%20Preview%20of%20Future%20Enhancements.pdf
By now, it can be done with undocumented options of the expire
Expiration is by node number. Numbers are assigned when the node is
registered with the TSM server. Using the beginnode and endnode
parameters of the expiration command you can perform selective
expiration. To get the node numbers use these case-sensitive commands
from a dsmadmc session.
create
It runs in the same order as the "q auditocc" output, which is the order
that they were registered on the server.
Ben
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Sung Lee
Sent: Tuesday, June 17, 2008 9:36 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [AD
If your goal is to fully remove a node's data from a storage pool,
rather than pruning certain files, see topic "Copy Storage Pool,
remove node from" in http://people.bu.edu/rbs/ADSM.QuickFacts .
Richard Sims
On May 19, 2008, at 5:09 PM, David Hensley wrote:
Question needing answered please. Is there a way to expire old data
in your
tape copy pools from a particular node?
dsmc expire -virtualnodename=
Dave,
Yes. I got this from IBM support.
expire inventory beginnode= endnode=
To get the node numbers, use the following case-sensitive commands.
>From a dsmadmc session:
create sqltable Nodes Mynodes
select c0,c1 from Mynodes order by c1
drop sqltable Mynodes
Cheers,
Jim Schneider
-Origina
On May 15, 2008, at 3:10 PM, David Hensley wrote:
I am running TSM server 5.5 on a Windows 2003 server. I want any data
residing in my copy pools (Onsite and Offsite) over 42 days old to
expire.
The volumes that expire their data should show up as EMPTY. Below is
a copy
of a script that runs on
Do you have a script that you can run to see how many reclaimable tapes
you have?
For the storage pools you show below run the following two:
select volume_name as ONSITE_VOLUME,est_capacity_mb as
CAPACITY,pct_utilized as UTILIZATION,pct_reclaim as RECLAIMABLE from
volumes where stgpool_name='HPON
6.02.13 at 09:05 [EMAIL PROTECTED] wrote:
Date: Mon, 13 Feb 2006 09:05:16 -0500
From: David E Ehresman <[EMAIL PROTECTED]>
Reply-To: "ADSM: Dist Stor Manager"
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Expire Inventory
Instead, you may want to run EXPire Inventory with Quiet=No
Does
>Instead, you may want to run EXPire Inventory with Quiet=No
Does the QUIET=NO vs QUIET=YES on expirations have much of an effect on
the overall speed of expiration?
David
Ian - It sounds like you're cursed with a high-churn environment...
You seem to have clients whose file population is greatly changing
over time, making for a lot of work for the TSM server. You can look
at Occupancy for your number of files in the TSM server, but that's
not going to tell you muc
Hello Karl,
we observed the same thing when we migrated from Version 5, Release 1, Level
8
to Version 5, Release 2, Level 0.
ANR0812I Inventory file expiration process 273 completed:
examined 421039003 objects, deleting 3974009 backup objects,
247900 archive objects, 0 DB backup volumes, and 0
re
1) Could take a while depending on how you changed your retention for example if you
went from 180 active version of a file to 20 then TSM would have to potentially expire
60xeach changed file. In additional WIN2k is not know for very fast I/O, not to
mention if your tsm db is not layed out in
>Sorry I should have included more information. I am running TSM server
>5.1.6.3 and we run expiration daily by way of administrative command. And
>I am sure that at least there should be more than 10% of all of our files
>should be inactive or considered for expiration as we have been running
>T
D]>
06/27/2003 05:08 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: expire inventory not looking at all files
expire inventory is only looking at inactive versions of files.
At 04:27 PM 6/27/2003 -0500, you wrote:
expire inventory is only looking at inactive versions of files.
At 04:27 PM 6/27/2003 -0500, you wrote:
I think I may have an issue. When Expire inventory runs it does not
appear to run through all of my files.
When I run the following sql statement I see many files but the expire
inventory endin
Roger Deschner
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: "ADSM: cc:
Dist Stor Subject: Re: expire inventory question
Manager"
&
How long does expiration take? Is it finishing? If not, you are in big
trouble.
What is your reclamation threshold? A good rule of thumb is to simply
set it to 50%, which is the default.
Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
( ) ASCII ribbon campaign
X aga
What about retv for t=a. I know that on TDP for SAP is it does everything
as archives so it may actually be your archives that aren't going away. You
do need to make sure that retv is greater then or equal to how long you keep
them in TDP.
Becky
-Original Message-
From: Rob Schroeder [m
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On
Behalf Of Jane Bamberger
> I had that problem with expiration - my mail server kept pinning the
> process - When it finally ran to completion it took 4-5 days, and expired
> 16M files.
Which goes to show that you simply *must* run a compl
Any other idea?
Tom
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Loon, E.J. van - SPLXM
Sent: Thursday, May 16, 2002 1:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Expire inventory (or audit license) hangs migrations and
back ups
Hi Tom!
I have seen this too
: "Jolliff, Dale" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 16, 2002 8:11 AM
Subject: Re: Expire inventory (or audit license) hangs migrations and back
ups
Another variation on the theme:
On a 4.1.4.1 server here we see the 'log pinned' situation a
ce a full expiration and hopefully that
will alleviate the symptoms a bit.
-Original Message-
From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 6:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Expire inventory (or audit license) hangs migrations and
back
Hi Tom!
I have seen this too a few days ago on my AIX server, running TSM 4.2.2.0.
It looks like some kind of deadlock on a logpage. You will see that the
expire inventory is just hanging and that one of your backup sessions is
hanging too.
You don't have to recycle the server though. As soon as y
THanks, I will try switching to CANCEL EXPIRATION instead of using DURATION,
and see if that works.
-Original Message-
From: Bill Colwell [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 5:12 PM
To: [EMAIL PROTECTED]
Subject: Re: EXPIRE INVENTORY shuts down
Wanda, I have seen
Wanda, I have seen this, sort of, and it is expected behavior, working as designed.
When you run expire with duration, or use the 'cancel expiration' command as I do,
the point where expire stops is recorded in the db. When you start it again
it starts at that point and continues either for the
al Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 2:54 PM
To: 'ADSM: Dist Stor Manager'
Cc: PINNI, BALANAND (SBCSI)
Subject: RE: EXPIRE INVENTORY shuts down
Thanks, but in my case it is shutting down when there is still a LOT of
things to expir
From: PINNI, BALANAND (SBCSI) [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 2:32 PM
To: [EMAIL PROTECTED]
Subject: Re: EXPIRE INVENTORY shuts down
Importance: High
Wanda
If the no of objects are to to be inspected or
Engineering
Wal-Mart Stores, Inc.
WAL-MART CONFIDENTIAL
-Original Message-
From: PINNI, BALANAND (SBCSI) [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 2:47 PM
To: [EMAIL PROTECTED]
Subject:Re: EXPIRE INVENTORY shuts down
of
>things to expire.
>When I restart it again, it starts up again and runs for hours.
>
>
>
>
>-Original Message-
>From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, May 30, 2001 3:32 PM
>To: [EMAIL PROTECTED]
>Subject: Re: EXPIRE IN
-Original Message-
From: PINNI, BALANAND (SBCSI) [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 2:32 PM
To: [EMAIL PROTECTED]
Subject:Re: EXPIRE INVENTORY shuts down
Importance: High
Wanda
If the no of
PROTECTED]
Subject: Re: EXPIRE INVENTORY shuts down
Importance: High
Wanda
If the no of objects are to to be inspected or inspected objects are
completed within time duration then it shuts off by itself.
In my case when I wanted to run for duration=10.
Then issued the cmd query proc I can see that as
FYI
Does it not expire inventory as client runs the backup !!!
-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 2:40 PM
To: [EMAIL PROTECTED]
Subject: Re: EXPIRE INVENTORY shuts down
Oh bimps.
Something else to script, that should happen
I have. We are on 3.7.0 (I know, bad idea but that is what I am stuck with
for now). We have to run expire three times. The first two stop
pre-maturely. The third time it takes off. We do this program wise. The
first scheduled program starts expire and makes a scheduled program to run
in 5 m
Wanda
If the no of objects are to to be inspected or inspected objects are
completed within time duration then it shuts off by itself.
In my case when I wanted to run for duration=10.
Then issued the cmd query proc I can see that as all objects get inspected
within the time it gets shuts off bec
Oh bimps.
Something else to script, that should happen automatically.
But thanks, I'm glad to know it's not just me.
-Original Message-
From: Ford, Phillip [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 3:34 PM
To: [EMAIL PROTECTED]
Subject: Re: EXPIRE INVENTORY shut
We had the same problem and applied ptf for 3.7.4 which allows the use of a new
parameter (skipdirs=yes) with the 'expire inventory' command. TSM's method of
expiring archive files was causing expiration to run extremely slow. The skipdirs
parameter solved the problem.
>>> "Lau, Ming" <[EMAI
I would like some more info also ...this could be a potential problem just
waiting to bite us in the rear.
Thxs
T
-Original Message-
From: Joe Faracchio [mailto:[EMAIL PROTECTED]]
Sent: Saturday, April 21, 2001 11:27 AM
To: [EMAIL PROTECTED]
Subject:Re: Expire
After the upgraded ADSM 3.1 to TSM 3.7.4, I have similar problem which
under investigate now. Larry, what exactly problem you have with Expire
Inventory. Missing volumes in storage pool??
Besides that, there is another problem I experienced. The "Maximum Mount
Points Allowed" @ client node wil
Could somebody elaborate on this teasing tidbit?
what kinda "problem ... not updating the database correctly"
I've upgraded from 3.1.2.20 to 3.7.2. recently and have not seen
any manafestations of this. That I know of.
More info would help ... thanks ...
joe.f.
Joseph A Farac
Thanks for response. By upgrading does it fix the current database ?
Larry Way
408-743-4242 Desk
408-655-3512 Cell
408-743-4201 Fax
>>> [EMAIL PROTECTED] 04/19/01 10:53AM >>>
Upgrade to 3.7.4.3. We had the same problem.
>>> [EMAIL PROTECTED] 04/19/01 01:14PM >>>
Recently upgraded from ADSM
Upgrade to 3.7.4.3. We had the same problem.
>>> [EMAIL PROTECTED] 04/19/01 01:14PM >>>
Recently upgraded from ADSM 3.1 to TSM 3.7.2. I believe there is a problem with
Expire Inventory not updating the database correctly. Anyone else experience this or
know of any problems ??
Thanks in advan
>I thought Expire Inventory was a 'constant' keyed off of how many files
>you have and not how many are deleted. This is interesting.
Joe - It is "interesting"... The task is indeed proportional to the
number of files that have expired, rather than the number of
files in the server. We h
To: [EMAIL PROTECTED]
> Sent by: cc:
> "ADSM: Dist Groups: Don't Expand
> Stor Manager"Subject: Re: "Expire Inventory" taking
>
Richard Sims
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: cc:
"ADSM: Dist Groups: Don't Expand
Stor Manager"Subject: Re: "Expire Inventory"
>We issue an expire inventory command on a daily admin schedule.
...
>Today, it is taking well over 1 hour to complete.
That might be the result of a retention threshold being reached,
or a large number of files having gone Inactive some time ago.
When the Expire Inventory completes, you will lik
> Sent: Wednesday, September 13, 2000 10:19 AM
> To: [EMAIL PROTECTED]
> Subject: Re: expire inventory - question on number of objects
> examined
>
> > What does the number of objects examined during inventory expiration
> > include?
>
> ADSM differentiates betw
> What does the number of objects examined during inventory expiration
> include?
ADSM differentiates between active and inactive backup files. A backup file is
always active when it first arrives from a client. A backup file changes to
inactive when the ADSM server finds out that the correspondi
75 matches
Mail list logo
