You are then in essence keeping deleted versions of files forever right ?
With "Versions Data Deleted: Nolimit"

Tim

----- Original Message -----
From: "Steven Harris" <sjharris AT AU1.IBM DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Thursday, June 05, 2008 8:13 PM
Subject: Re: Backup retention question

Hi Bruce

IMO the best way is

             Versions Data Exists: Nolimit
             Versions Data Deleted: Nolimit
             Retain Extra Versions: 7
             Retain Only Version: 7

This guarantees that the data will be kept 7 days.  With your setup, if
someone runs a selective, or an extra incremental in the middle of the day
on a file that has changed, the last version will be pushed off.  Also, as
a bonus, expiration processing is more efficient where the versions
parameters are not in play.

HTH

Steve

Steven Harris
TSM Admin, Sydney Australia




            "Dollens, Bruce"
            <BDollens@TXFB-IN
            S.COM>                                                     To
            Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
            Dist Stor                                                  cc
            Manager"
            <[email protected]                                     Subject
            .EDU>                     [ADSM-L] Backup retention question


            06/06/2008 06:10
            AM


            Please respond to
            "ADSM: Dist Stor
                Manager"
            <[email protected]
                  .EDU>






We are wanting to setup a new policy domain and management class for our
Active Directory backups.  We want to keep only 7 days of backups. If I
wanted to accomplish this would the management class look like this? (I
have a difficult time with this part of it for some reason).

                          Versions Data Exists: 7
             Versions Data Deleted: 7
             Retain Extra Versions: 7
             Retain Only Version: 7

Thanks!