Guys,

Another option, which has the cost of another ADSM client licence, is to
register a second node name for your client and run an incremental
backup on a monthly basis on that client using that second node name.
Create a mgmtclass with a versions data exist of 6 or 7 and a retain
extra versions of 185 days or so.  You get the benefits of ADSM's true
incremental without it interfering with your daily backups.  Note, you
may also want to set the frequency parameter on the backup copy group to
28 or 30 days so that if a backup is done accidentally against that
second node name in the middle of the month, it won't back up files that
were backed up 15 days previous.

Cheers...
Bruce

"Lambelet,Rene,VEVEY,FC-SIL/INF." wrote:
>
> Hello,
>
> you are right, an archive is like a selective (full) backup. Therefore we
> kepp our archives to a strict minimum, specifying the desired filesystems or
> directories in the archive command. Remember: archive do NOT understand
> Excludes...
>
> What we archive are : source programs , access MDB's, databases if no agent
> is available to do online and incremental backups, Backint data (SAP)...
>
> Regards,
>
> Rene Lambelet
> Nestec SA - 55, Av. Nestle - CH-1800 Vevey
> Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
> E-Mail: rene.lambelet AT nestle DOT com
>
> > -----Original Message-----
> > From: Magura, Curtis [SMTP:curtis.magura AT LMCO DOT COM]
> > Sent: Tuesday, January 26, 1999 8:46 AM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Archive vs. Backup
> >
> > I've been following the comments on using Archive to meet the requirements
> > of long term data storage asked by someone else on the list. I have the
> > same
> > sort of requirement and imagine most everyone does. Our requirement is 30
> > copies plus 1 monthly copy kept for 6 months.
> >
> > If I understand Archive correctly I will be making a complete copy of my
> > data and keeping it in an Archive pool. Does this mean that I am basically
> > doing a complete copy of our disk farm every thirty days? With the ever
> > growing size of disk farms that seems to be a problem. Based on the
> > performance of our daily backups it would take days and days for this to
> > complete for us.
> >
> > At this point I've set versions to 9999 and age them off at 186 days.
> > Granted this creates way more than the number of copies than I want to
> > keep
> > or have a requirement to keep. We have over 1 TB of disk spinning ...I'm
> > sure I'm missing something here. Everytime I read the Sys Admin Guide
> > discussing the setup and management of storagepools I think I have it
> > until
> > I starting thinking about it again!
> >
> > For some of the larger shops out there ... Do you make Archives of
> > everything on some interval ? If you do what kind of timeframe for
> > completion of the Archive?
> >
> > Curt Magura
> > Lockheed Martin
> > Enterprise Information Systems
> > Gaithersburg Md.
> > 301-240-6305