ADSM-L

Re: How can delete common filespace in datbase directly.

2003-03-11 16:36:00
Subject: Re: How can delete common filespace in datbase directly.
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 11 Mar 2003 14:35:51 -0700
TSM does not permit deletion of individual files, directories, or portions
thereof.

One way to accomplish this indirectly:

1) Define a new management class with attributes that look something like
this:

   verexists=1
   verdeleted=0
   retextra=0
   retonly=0

   def mg standard standard delete
   def co standard standard delete vere=1 verd=0 rete=0 reto=0
   act po standard standard

2) Define a client option set and clientopt like this, and associate with
the desired nodes:

   def clo delete
   def clientopt delete inclexcl "include /.snapshots/.../* delete"
   upd n node1 clo=delete
   upd n node2 clo=delete
   etc.

3) Next time the nodes run an incremental backup, all files in /.snapshots
will be bound to the "delete" management class.

After that is done, delete the inclexcl client option and define a new
one:

   q clo delete

      note the sequence number for the inclexcl defined above

   del clientopt delete inclexcl seq=0

      (sequence numbr is 0 in my example)

   def clientopt delete inclexcl "exclude.dir  /.snapshots"

Then when the clients next run incremental backups, all the backup
versions will be eligible for expiration next time EXPIRE INVENTORY runs.

A simpler implementation of the whole thing is as follows:

   def clo delete
   def clientopt delete inclexcl "exclude.dir  /.snapshots"
   upd n node1 clo=delete
   upd n node2 clo=delete
   etc.

Then when the next backups run, the files will be expired. The difference
in this approach versus the more extensive one I described above is that
the files will not expire as quickly; that is, in my first approach, the
files will be deleted from TSM's inventory much more quickly because they
are being rebound to a management class with the lowest possible retention
values. The second approach will cause the files to expire per the
criteria of their current management class.

Note that in both cases, the directory structure (dirs, not files) will
expire based on their assignment management class (the one with the
longest RETONLY value). But this should otherwise help accomplish what you
wish.

You may want to delete the "delete" management class and cloptset when you
are done.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"PINNI, BALANAND (SBCSI)" <bp3965 AT SBC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/11/2003 12:48
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        How can delete common filespace in datbase directly.



All-

I know that we can delete filespace by node name .But I want to delete
from
database the follwing structure--So that any entry for this structure in
database get deleted.
  /.snapshots/../../..

How can do that so that all structure for all nodes gets deleted.
It does not accept node=*????

Thanks
Balanand Pinni