>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
I thought Expire Inventory was a 'constant' keyed off of how many files
you have and not how many are deleted. This is interesting.
I've heard of shops that only run it on weekends because it takes so long
which I don't understand. It's "cancelable" and its "restartable" and so
why not run it d
Richard, you were right one.
After the "expire inventory" was completed, I did the "q occ" (query
occupancy) and we had about 6GB of AIX files expire on one of the AIX
servers.
That explains it!!
I just never observed this and was concerned as we all are when "unknown"
occurrences are observed.
>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
We issue an expire inventory command on a daily admin schedule.
We have ~1.6M objects in the TSM db.
It normally takes ~10-12 minutes to complete.
Today, it is taking well over 1 hour to complete.
We have no unusual activities occurring that I can see.
Does TSM so some "extra" checking on a
