OnDemand User Group
Support Forums => MP Server => Topic started by: SacramentoUser on January 11, 2019, 12:45:36 PM
-
We run CMOD Multiplatform on RHL. All of our archives reside in cache. When we converted to CMOD our consultants didn't set up ARSMAINT to run on a scheduled basis. As our cache grows, we have been testing ARSMAINT and want to schedule it to run in production.
When does everyone else out here run ARSMAINT? The documentation says to run when very little else is running. That is a challenge given the complexity of our systems. Input is coming in from multiple platforms and systems including ICC SAP.
Any advice would be great.
-
CMOD doesn't need a lot of maintenance.
Since you've never run it before, run it on one of your smaller Application Groups first (using the -g option), and get a taste for how it affects system performance. Then do a few more, then maybe one of the larger AGs. Then automate it to run on your 'quietest' day of the month. It really doesn't need much more than that unless your volume of data is in the hundreds-of-terabytes range.
There's also an article on the wiki for the IBM CMOD arsmaint command: https://cmod.wiki/index.php?title=arsmaint
-JD.
-
Thanks. :)
-
ARSMAINT has two main modes -d (data expiry) and -c (cache expiry).
The -d does document EXPIRY (careful if you never ran this) as it will purge production documents forever !!
You have also mentioned "All of our archives reside in cache." Not sure if you mean using Cache as a primary storage;
in which case the cache maintenance "-c" will not do anything
or
each AG is also cached while using other primary storage e.g. TSM or a Cloud Service. In this case the -c "The cache maintenance" will purge cache only while keeping the document(s) in the main storage area, and it is safe to use.
Otherwise, as Justin mentioned run it first on a small AG first, ideal in a test env and review system log afterwards, also it is good take df -m /my_cache_dir before and after so you could see how many MB was released.