ADSM-L

Expiration takes weeks

2002-03-19 14:16:34
Subject: Expiration takes weeks
From: Tab Trepagnier <Tab.Trepagnier AT LAITRAM DOT COM>
Date: Tue, 19 Mar 2002 13:13:07 -0600
TSM 4.1.5.0 on AIX 4.3.3 PL 8
Client is 3.1.0.7 on Irix.

We have a node that is a CAD file server.  For a long time we've been
running Expire Inventory SkipDir=Yes as a workaround to the expire
directory problem in TSM.

Recent notes in the forum has said that if you let a SkipDIr=No expiration
just run, it will "eventually" finish.  So I tried it.

Two weeks ago.

So far it has examined about a million objects associated with that node,
but it is still chewing on that node's data.  Running AIX topas shows that
all the DB disks are in constant use reading data.  At intervals of a few
minutes to an hour or so, the CPU load will shift to high User and Kernel,
and lots of updates will get written out.  Then the process restarts the
long reads with no updates.

For those who haver reported this phenomenon, and have allowed expiration
to "eventually" complete, how long did that take?

And if I tried to retrieve an archive from this node, could I also expect
to wait two weeks (or more) to get the file list?  Past attempts at archive
retrieval have been abandoned after more than 24 hours.

Thanks.

Tab Trepagnier
TSM Administrator
Laitram Corporation
<Prev in Thread] Current Thread [Next in Thread>