Guy,

I would keep my BACKUPS the same and do a specific ARCHIVE of the
relevant files which need to be stored for specific periods of time.
You would need different ARCHIVE management classes for each time
period.  This would mean you would keep 2 copies of certain files on
ADSM for the 28 days after each of these periods but that is no big
deal.  This is exactly what ARCHIVE is meant for.

Cheers,
Simon
----------
| From: ADSM-L AT VM.MARIST DOT EDU; guy_sheppard AT UK.CU DOT COM
| From: ADSM-L AT VM.MARIST DOT EDU; guy_sheppard AT UK.CU DOT COM
| To: ADSM-L AT VM.MARIST DOT EDU
| Subject: Please Help - Backup retention
| Date: Monday, 25 January, 1999 10:54PM
|
| 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.
|