We have a similar scenario....

For short term retention (5 years or less), we use dual node names Node_ARC
and send their data to a backup management class that functions for an
incremental archive. The downside is our database and dirmc size will
continue to grow for 2 years.

For long term retention (>5 years) traditional archiving is the way to go.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Pasquale, Joe
Sent: Tuesday, November 18, 2003 11:08 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Catalog Size and large number of files


Full backups are required because of retention requirements set by
government regulations, so the "incremental forever" philosophy is NOT a
solution.

-----Original Message-----
From: David E Ehresman [mailto:deehre01 AT LOUISVILLE DOT EDU]
Sent: Tuesday, November 18, 2003 11:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Catalog Size and large number of files


> If so, could you please forward some
>possible solutions?
>

The obvious solution is to use TSM's "incremental forever" philosophy and
not do unnecessary full backups.

David


*********************************************************************
This message and any attachments are solely for the intended recipient. If
you are not the intended recipient, disclosure, copying, use or distribution
of the information included in this message is prohibited -- Please
immediately and permanently delete.