Joni When I've done this in the past I like to create a new "named" management class for each application that is doing long term archiving, even if the requirements are the same as an already existing class. The reason for this is that if requirements change for this one app, and they suddenly need 10 years or 3, or you need to put that to an out of library storage pool, you can just change the one copygroup definition and the change is made, without affecting any other app's data.
Also I don't like to name long term management classes with their retention periods as you have done because system admins will find your class and decide it would be a good idea to back stuff up for 7 years - and you will have no idea that it is happening. HTH Steve Steven Harris TSM Admin Sydney Australia "ADSM: Dist Stor Manager" <[email protected]> wrote on 08/11/2007 08:39:57 AM: > To expound on Richard's admonitions about the size of the archive, > consider a slight modification: > > objects="c:\archive7yr\,d:\archive7yr\" > > Have your users place files they want archived into that directory with > the knowledge that you back it up on a monthly basis. Then delete the > contents of the directory. > > Kelly J. Lipp > VP Manufacturing & CTO > STORServer, Inc. > 485-B Elkton Drive > Colorado Springs, CO 80907 > 719-266-8777 > [EMAIL PROTECTED] > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Richard Sims > Sent: Wednesday, November 07, 2007 1:26 PM > To: [email protected] > Subject: Re: [ADSM-L] Backup schedule syntax? > > On Nov 7, 2007, at 2:05 PM, Joni Moyer wrote: > > > ... > > options="'-archmc=arc2555 -subdir=yes" objects="c:\* d:\" > > I believe that should be: > options="-archmc=arc2555 -subdir=yes" objects="c:\* d:\*" > > Be prepared for a great increase in your TSM server space utilization > every month, as Archive is unconditional, and so will result in the same > old data being archived again and again. Also, unless you have the > right Excludes prepared, you will be archiving everything on the drives, > which seemingly will include a lot of system files which will be > worthless space-consumers in the archive storage pool and database. > > Richard Sims
