Difference between revisions of "arsmaint"

The IBM Content Manager OnDemand arsmaint command performs routine maintenance on Content Manager OnDemand servers. Maintenance can consist of migrating CMOD data from Cache to Archival storage, removing data from the cache to make room for new data, or deleting expired documents and metadata.

The CMOD arsmaint utility must be run by the instance owner - that is an operating system account, usually named 'archive' or 'odadmin'. There are several command line options for CMOD's arsmaint utility:

:The -e option for the arsmaint command migrates index data to long-term archival storage. This option is rarely used because of the relatively low cost of disk storage, and the performance impact on queries.  

:The minimum percentage capacity that arsmaint will try to empty the cache filesystem to. Use this command to clear out the arscache filesystems in preparation for an unusually large load of documents into Content Manager OnDemand.  

:The maximum percentage capacity of the arscache filesystems that arsmaint will allow to remain empty.  

:This option records an alert message in the Content Manager OnDemand System Log, and prints an error message to stdout (for UNIX/Linux) or the console (on Windows system) when the cache filesystem exceeds the specified percentage. An alert from this option indicates that the arsmaint command was not able to remove enough data from the cache to make additional space for new data. You'll either need to adjust the caching settings for your Application Groups, or add more storage to the Cache Filesystem.  

:The -m option migrates data from cache to long term archival storage if your IBM CMOD server has secondary storage is defined, and your Application Group is configured to use it.

:This arsmaint command runs database statistics. Collecting (or updating) database staticstics for IBM CMOD helps improve query performance. Because Content Manager OnDemand is an archival product, database statistics do not change dramatically on a day to day basis. Running statistics is only recommended once every week or two.  In addition, you may want to run database maintenance with the CMOD arsdb command before collecting statistics with the arsmaint command.  

:Specifies the password, or path to the IBM CMOD stash file.  

:Specifies the trace file. Contents of the trace will be written to this file & path.  

:Specifies the trace level. A numeric value will determine how much detail is written to the trace file.  

:Even if the Expiration Type is set to 'Load', which would normally perform better than the 'Document' setting, if you have an extremely large number of loads of small documents into the Application Group (in the millions), then the arsmaint expiration process is very similar to Document expiration instead.  

:If your system has a large number of documents to expire from IBM CMOD, then the arsmaint command may run for an extended period of time, as it performs the work required. If your Content Manager OnDemand server includes a Tivoli Storage Manager server for storing archival data, the expiration process may run more slowly as CMOD sends requests to TSM for the documents to be deleted.

 

[[Optimizing Cache Filesystems]]