ADSM-L

Re: Expiration

2007-02-07 13:44:39
Subject: Re: Expiration
From: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 7 Feb 2007 13:44:05 -0500
-----Kevin Boatright wrote: -----

>Is there any way expire inventory on all nodes except for a select
>few? I have two servers that I cannot delete any data on.
>
>I changed the management class on thse two servers to not delete
>files. The management class has been changed on active files but
>not on inactive files. But, when expiration runs next, it will
>delete the inactive files.
>
>Any recommendations?

A long time ago my site had a problem that caused expiration to
hang at a certain directory. IBM informed us of undocumented
options to the 'expire inventory' command to control the first
and last nodes processed (nodes are processed in order of
registration time). We alternated between expiring from the
oldest node to the one just before the problem node, and
expiring from the node just after the problem node to the
newest node. I don't know whether these options still exist
in the current server code. I couldn't find my notes on that
episode.

I am not sure this type of facility would help you. Other
sites have tried to keep files restorable by suppressing
inventory expiration. If I remember correctly, they found
that the client would not restore or even list files that
were eligible for expiration, even if the files had not
in fact been removed from the TSM database by inventoryexpiration.

<Prev in Thread] Current Thread [Next in Thread>