ADSM-L

Re: Forcing Expiration in TSM

2003-09-03 19:21:10
Subject: Re: Forcing Expiration in TSM
From: "Stapleton, Mark" <stapleto AT BERBEE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 3 Sep 2003 18:20:52 -0500
From:   Rothecker, Chris ISC [mailto:Chris.Rothecker AT ISC-ONLINE DOT CA]
>This sounds like what I want to do.  Any idea how to make it happen.  I
poked through the admin guide and there is a section that tells you it can
be done but it doesn't say how to actually do it.<

Simple.

1. Create a new management class with desired backup copy group settings 
(retention period, number of files retained, etc.).

2. Modify include/exclude list (either in local client option file or in client 
option set on server) for files to be modified:
   include  c:\data\moredata\...\* <new_management_class_name>

3. Backup the TSM client. This will cause all affected files to be rebound to 
new management class.

4. Allow expiration to run normally.

You're done.

--
Mark Stapleton (stapleton AT berbee DOT com)

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