>This is, I think, true, but the result is that ADSM has version that are
>unknown to SBT, and so, unusable.  The essential option to keep ADSM and
>SBT in sync is RETONLY=0.
>
>
>
>At 01:28 PM 10/21/99 -0400, you wrote:
>>I believe that ADSM rules apply. SQL-BACKTRACK simply issues delete
>commands per its definitions.
>>
>>>>> "Glass, Peter" <Peter.K.Glass AT NORWEST DOT COM> 10/21/99 12:44PM >>>
>>We have an SQL-BackTrack client who has their file expiration set for 30
>>days, within SQL-BackTrack.
>>The ADSM expiration rules for these backups are to keep a maximum of 10
>>versions, with a 180 limit for the only backup version. SQL-BackTrack
shares
>>the same STANDARD management class with the majority of our clients.
>>If our SQL-BackTrack backs up the same files daily, does ADSM expire them
>>according to the 10 version limit, that is, after 10 days?
>>Or will ADSM honor the SQL-BackTrack expiration limit of 30 days?
>>If anybody can demonstrate their knowledge and expertise on this topic,
they
>>will have an appreciative audience.
>>Thanks!
>>
>>Peter K. Glass
>>Distributed Storage Management
>>Norwest Services, Inc.
>>*612-667-0086   *612-899-2776
>>*<peter.k.glass AT norwest DOT com>
>>
>Fred Johanson
>System Administrator, ADSM
>S.E.A.
>University of Chicago
>773-702-8464
>