You can only use management classes to implement different
retention policies for different files. You can not implement
different retention policies for the same file without using the
archive command.

Your best option is to retain your daily backups for 14 (or 28,
whichever is your requirement), and then do archives at month-end
and quarter-end with a retention of a year, an archive at tax
year-end and financial year-end for 5 years.

 -- Tom

Thomas A. La Porte
DreamWorks Feature Animation
tlaporte AT anim.dreamworks DOT com

On Mon, 25 Jan 1999, GSHEPPAR@CUUKMAIL wrote:

>To:         I1017261@IBMMAIL   IBMMAIL -I1017261 *ibmmail.I1017261
>Dear All,
>
> No responses yet - Please help
>
>  The current retention requirements I'm working to are keep backups for 28
>days - Simple enough.
>
> The business now require daily backups kept for 14 days (In this case they are
>Oracle DataBase dumps) We're not using EBU, RMAN or SQL Backtrack.
>
> Month end for 1 year
>
> QTR end for 1 year
>
> Tax year-end for 5 years
>
> Financial year end for 5 years
>
> etc etc etc.....
>
> My understanding is that ADSM can be made to do this by defining differing
>Management classes. However, in order to attach those management classes to
>each of the differing backups; I'd have to have multiple options files and keep
>manually switching them depending on the requrements.
>
> Please advise if I'm talking rubbish !!!
>
> Thanks, Guy.
>