Removing Old Documents from TSM

[rstockton]

We have a situation where release 8.4 did not expire documents from TSM.  It did remove them from DB2 and CMOD but because of a glitch in 8.4 (patch has been added to correct the glitch) they were not removed from TSM.  Does anyone know how we can identify and remove them from TSM?

Thanks,
RS

[rstockton]

Would running the Expire Inventory process remove the old orphaned documents from TSM based upon the TSM policy for the node?

[Alessandro Perucchi]

Hello,

Well I don't know exactly how you can do that, maybe open a PMR with IBM would help on that case.

In all cases, to identify for a storage node what are the document that are not anymore in the application group in CMOD, I would do the following:

1) get the AGID NAME from all the application group having documents in the storage node.
2) search for all doc_name in all the application group segments (normally just the first part (you know number + FAA (sometimes GAA)) get the uniq sorted list.
3) compare to the files in the storage nodes which are not in the list gathered in 2)
4) you have the list of all potential files in TSM that could be "deleted"

Just for an example

you have a Storage node called SN1 in the CMOD ARCHIVE Instance
you have only application group AGTest archive documents in this storage node, with the AGID NAME NWA
You have only 1 segment : NWA1, and by doing a "select distinct doc_name from NWA1", you get the following:

1FAAA
2FAAA
3FAAA
6FAAA

and if you look in TSM in the SN1 storage node, you will have something like:

ARCHIVE/NWA/1FAA
ARCHIVE/NWA/2FAA
ARCHIVE/NWA/3FAA
ARCHIVE/NWA/4FAA
ARCHIVE/NWA/5FAA
ARCHIVE/NWA/6FAA

since 4FAA and 5FAA are not in the NWA1 segment, these are the files that potentially could be deleted from TSM without any data loss.

Regards,
Alessandro

[rstockton]

Thanks Alessandro.

One more question.  My knowledge of TSM is limited, what command would I use to find the following information?

------------------------------------------------------------------

and if you look in TSM in the SN1 storage node, you will have something like:

ARCHIVE/NWA/1FAA
ARCHIVE/NWA/2FAA
ARCHIVE/NWA/3FAA
ARCHIVE/NWA/4FAA
ARCHIVE/NWA/5FAA
ARCHIVE/NWA/6FAA



Thanks

Russell

[sandeepveldi]

Russell,
If you have administrative rights on TSM, you can issue a query on the TSM DB. Here's a sample query that'll give you the list of all objects under a filespace NWA and storage node SN1

select * from archives where node_name="SN1" and filespace_name="/NWA"

Note that you have to issue this query in the TSM admin console (on AIX environment, you can reach the TSM admin console by running dsmadmc)

Thanks
SV

[rstockton]

SV.

Thanks for the rsponse to the post.  I will try this.

Thanks,

Russell

[pankaj.puranik]

From what I understood, it is dangerous to do delete object 0 objectID.

I also came to know that there is a utility arsexoam for OAM that deletes objects from OAM.

Is there such a utility available for TSM also?

[Alessandro Perucchi]

Hello Pankaj,

in that case, this tool is called CMOD... you use CMOD tools in order to delete objects, like for example arsdoc delete (ok only the index :-) or arsadmin unload.
Any other direct way is not advised. Even if possible. Especially if possible.

Sincerely yours,
Alessandro