Thats what the TYPE=ARCHIVE is for.  Default is to do all types



"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 23/01/2008
10:16:11 AM:

> Thanks. You should have seen my efforts to get it cut down from the
> original version ;-)
>
> I got the impression from the BAClient redbook that delete filespace
> would remove backup AND archived copies. Is that incorrect?
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Steven Harris
> Sent: 22 January 2008 22:54
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Another archive/expire query
>
>
> Angus,
>
> Congrats to your organization for the longest disclaimer in the history
of
> the internet :-)
>
> If its a whole drive,
>
> DEL FILESPACE node_name filespace_name TYPE=ARCHIVE
>
> on the server might be the way to go.  As its windows you may have to use
> the fsid number and nametype=fsid to indicate the drive you want.
>
> Regards
>
> Steve
>
> Steven Harris
> TSM Admin, Sydney Australia
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 23/01/2008
> 08:45:37 AM:
>
> > I am busy helping an external supplier understand his own Tivoli
> > system, which has become full.
> >
> > We plan to archive certain drive letters attached to a file server
> > which contain data that will never change. The archive process is
> > fine but what is the best way to remove references to the archived
> > data from the main TSM database? Should I run a
> >
> > dsmc expire j:\*.*
> >
> > at the client? Will that expire the data immediately? How would
> > subdirectories be handled? There appears to be no -subdir=yes option
> > for the expire command. Alternatively, would
> >
> > dsmc delete backup j:\* -deltype=all
> >
> > get rid of the file references from the TSM database? I take it the
> > deletion would get rid of the entries immediately.
> >
> > Sorry for the probably newbie queries. I haven't done any archiving
> > before and it isn't my data ;-)
> > Angus
> >