ARSADMIN vs ARSMAINT

[jeffs42885]

Greetings all,

I need to purge some QA data that is no longer being used. I have a folder and application group (1:1) that I need to purge between a specific date range. The application group is setup to load to cache, and uses the following expiration settings:

-Cache Data for 9999 days
-Life and data of indexes never expire, with expiration type of load.

There are a few application groups that I have already removed the required data from, using ARSADMIN UNLOAD. However, this application group contains over 2,700 files between my date range of 01/01/2000 and 12/31/2010. I have never manually ran the ARSMAINT command to perform this, and I am not 100% positive it is what I am looking for. I need to remove the data, and remove all indexes to it.

/arsmaint -deimr -g   APPGROUP -I INSTANCE -p PASSW0RD -u ODUSER

[Justin Derrick]

It might make more sense to duplicate the AG/App/Folder and just delete the old one.  If you need to keep some data from that group, use 'arsdoc get' to fetch the data you want, and load it into the newly defined AG. 

Once the old group is deleted, you can rename the new one to match the name of the old one, and everything goes back to normal. 

Let us know how it goes!

-JD.

[jeffs42885]

Heres what I ended up doing. I did this in our development environment and it worked. I need to purge all documents in a specific application group older than 411 days old.

On the development server, The storage set is TSM DR-550, and its set to never expire. I changed the expiration date to 411 days and ran this command:

sudo -S arsmaint -deimr -g Appgroup -I instance -p password -u oduser

The process ran for approximately 10 minutes, and it purged all data in that application group older than 411 days. I need to run this same command on our test box which users are constantly using. The storage settings for this application group is Cache-Only library server, Should I set the Cache data and life and data of indexes to 411 days, and run this command also?

[Justin Derrick]

You shouldn't need to tweak it - depending on your expiration type, arsmaint should clean up the objects as well as the rows in the database table.  My understanding is that the expiration type of 'segment' doesn't issue an explicit delete of objects (in cache or TSM), but from your description, it doesn't sound like your expiration type is segment.

[jeffs42885]

Thanks for clarifying justin. Worked great for me :) I have one more question. The application groups that I needed to remove that were stored in cache, is there any way to determine which cache file system they are going to? AIX btw.

/sandbox/arscache1    37.38     13.52   64%   207804     3% /arscache/cache1
/sandbox/arscache2     37.39     13.52   64%    76106     1% /arscache/cache2

[Justin Derrick]

Nope, CMOD distributes loaded files across cache filesystems -- so your Application Groups are intermixed between both, and that's perfectly fine.

-JD.