In light of this, what would be the best way to protect a node's data from
expiring at all??  To keep from both active and inactive versions expiring??
If we rename the node and filespace, would the time based retention rules
eventually get the data?? Or since the new (renamed) node name never has a
backup, we are ok.  Perhaps moving the node to a policy domain with
unlimited retention is the only way to protect both active and inactive
files??


Just trying to understand this more....


Regards,

Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte and Touche USA LLP



-----Original Message-----
From: Richard Sims [mailto:rbs AT bu DOT edu]
Sent: Thursday, January 16, 2003 6:26 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Quick expiration question


>Just a quickie. When an inremental backup runs, some files get expired.
>Does this mean that they are 'marked' for expiration, but only get
>deleted from the database when the Expire Inventory job is run?

File expiration candidates processing based upon versions (number of same
file) is performed during client Backups (in contrast to time-based
retention rules, which are processed during a later, separate Expiration).

  Richard Sims, BU
- This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.