Hello Troy,

To answer you question...woraround for db2adutil limitation which does not
allow a user
to specify a management class - use 'TAKEN AT' option to point to a
_specific_
object you want to deactivate, for example:

db2adutl delete full taken at 20030501162656

Also, it make sense to request a DCR to be opened for db2adutl to
implement
a new option to allow a user to specify a particular management class he
wants
to query...or you can write you own application to utilize TSM API
dsmDeleteObj()
function to deactivate those objects.

Or, you can simply create two MCs (one for logs and weekly backups, and
another for daily ones), set retention settings to 8 and 1 weeks and then
deactiate ALL objects on the same day they were backed up! Sure, they
would be inactive, but TSM server will keep them for exactly 8 and 1 weeks
and then they will be expired (deleted) from the TSM server database.


Sergey, TSM L2 support,
San Jose, CA







"Tudor,Troy,VEVEY,GL-IS/IT" <Troy.Tudor AT NESTLE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/02/2003 03:44 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        DB2 Different retention policies for different backups.



Hi TMSers

We want to implement a backup policy like:

DB2 weekly online backup retained 8 weeks
DB2 daily online backup retained 1 week
All database logs retained 8 weeks

This of course allows us to perform a point in time recovery to any time
in
the last eight weeks, however recoveries more than one week old will
require
more effort.

We would assume use different management classes to separate out weekly
from
daily backups.
However tool db2adutl does not allow specification of different management
classes when marking backups inactive.

Any insight on how different sites manage such a policy would be welcome

Thanks
Troy Tudor