Just off the top of my head (and because I've had to look at similar
requirements) -- I'd set up a pair of management classes tied to archive
copygroups. Set one with a 366 day (or slightly longer) retention, and
build an archive process to run on the client monthly, eleven times per
year. Set the second one up with the retention for 15 years, and run it
on the twelfth month.

Tom Kauffman
NIBCO, Inc.

> -----Original Message-----
> From: Tom Smith [SMTP:tom1014 AT HOTMAIL DOT COM]
> Sent: Wednesday, December 23, 1998 10:34 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:
>
> Hi,
>
> does anybody know a workable solution for the following demand on
> policies my management agreed on with our customers:
>
> We want a daily incremental backup,
>  once a month a full backup, which should be kept for 1 year
>   once a year one of these month-backups should be kept for 15 years.
>
> (looks a lot like the son-father-grandfather principle)
>
> My site is looking at about 500Gb backed up data, which will be
> 2 Terabytes next year.
> Our adsm server runs on aix, with a 3494 robot (3 3590 drives)
>
> Thanks , and happy holidays, Tom
>
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com