I'm not sure if this is "Best" practice, but its what we do with our SQL
Servers and I imagine it would work with exchange..

We have three node names in three domains.
Exchange-exch (daily backups kept for 7 or 30 days for quick restores,
do a [first] Sunday full, then diffs the rest of the week [or month]).
Exchange-month (last Sat full backup with a 365 day retention).
Exchange-Annual(or year) (last Sunday of Dec. with 3650 days retention).

Each node would have its own schedule, and you have to work out the
conflict that will occur once a year with the Annual and the Exch node
on Sunday.  Of course you could do the annual on Monday after the diff
finishes.  If you do 30 day retention the conflict is easy to resolve
between the Weekly fulls.  Just do the monthly full on the first Sunday,
and the annual on the last, then schedule the last for after the
differential finishes.

The reason for the different domains is that it keeps it simple from a
management class assignment perspective.  Its easier not having to make
sure you adjust all that right in opt files and scripts.

As you can see you have options.  :-D

See Ya'
Howard
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steven Harris
Sent: Monday, March 10, 2008 12:50 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Exchange monthly yearly

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?

Thanks

Steve.

Steven Harris
TSM Admin
Sydney Australia