I snagged this little tidbit from a backing up databases manual......
SQL-Backtrack determines the names fo the objects that it stores on the adsm
server.  Each object receives a unique numerical name, so each successive backup
creates a different object name.  Therefore, only one copy of an object is ever
stored on the adsm server.  For this reason the management class  copygroup
option verexist=1 should(could) be used for the SQL-backtrack data.





"Glass, Peter" <Peter.K.Glass AT NORWEST DOT COM> on 10/21/99 11:44:51 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



 To:      ADSM-L AT VM.MARIST DOT EDU

 cc:



 Subject: SQL-BackTrack  Expiration vs ADSM Expiration







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>