Steven,

The technique that Howard described is what many customers do for
Data Protection for Exchange as well.
For example, you would have multiple node names with different policy
settings:
     EXCSRV33 - for regular daily backups (with management class to keep
for 90 days)
     EXCSRV33_MONTHLY - for monthly backups (with management class to keep
for 1 year)
     EXCSRV33_YEARLY - for yearly backups (with a management class to keep
forever)
You can manage the data and the schedules separately for the different
purposes.
Your idea of a COPY backup with different policy settings is also used by
some customers.
Using this technique, enables them to share one nodename for the daily and
monthly backups.
This way they can bind the COPY backups to their monthly retention needs,
and simply have the different nodename for their yearly backups.

Thanks,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/10/2008
01:50:08 AM:

> Hi All
>
> I have a multinational client (= worldwide standards and totally
> inflexible) who wants monthly backups - kept for a year - and yearly
> backups - kept for 10 years - of their exchange server.
>
> This is the first time I've had this requirement for exchange and am
> looking for some best practices.
>
> I can see the COPY backups, and they might be useful to do a monthly,
and
> I'm considering an an annual export of the appropriate monthly filespace
> with filedata=backupactive to handle the yearly requirement.
>
> Am I on the right track?