Hello,

I would advise to use Archive and not Backup function for such different
retention periods. Just define corresponding management classes and code
them appropriately in the archive command.

Regards,

Rene Lambelet
Nestec SA - 55, Av. Nestle - CH-1800 Vevey
Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
E-Mail: rene.lambelet AT nestle DOT com



> -----Original Message-----
> From: GSHEPPAR@CUUKMAIL [SMTP:guy_sheppard AT UK.CU DOT COM]
> Sent: Monday, January 25, 1999 3:49 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Please Help - Backup retention
>
> 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.