I handle this requirement with a SECOND client on each machine which does
an INCREMENTAL backup bound to a management class with the appropriate
retention time.  This eliminates the resending of static data.  This is
easily accomplished with a second dsm.opt file and a second server stanza.

Orville L. Lantto
Datatrend Technologies, Inc.  (http://www.datatrend.com)
121 Cheshire Lane #700
Minnetonka, MN 55305
Email: Orville.Lantto AT dtrend DOT com
V: 952-931-1203
F: 952-931-1293
C: 612-770-9166




"Cook, Dwight E" <DWIGHT.E.COOK AT SAIC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/04/02 11:01 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Monthly Backups, ...again!


ARCHIVE !

I tell clients, if they HAVE to have data for a SPECIFIC period of time,
archive it into a management class with the required retention period.

I try to only give them 1 3, 6, & 12 month management classes...
anything longer than that and I make them archive to a specially
registered
node name, I export that data, send the export tapes offsite and purge
that
specific info out of my TSM data base ;-)



Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suit 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109