arsmaint has stopped working post CMOD upgrade from 8.5 to CMOD 10.5

[mayank81089]

Hello,

We have observed that since we have gone live with CMOD 10.5.0.5 which was an upgrade from CMOD 8.5 the arsmaint utility is not working. As the cache storage size has increased exponentially, we have TSM client node registered as our archive storage solution however we are also maintaining one copy of the documents inside cache folder as well that is for 90 days only. We tried opening documents which have been stored in CMOD for more than 90 days but still see them coming from cache node instead of TSM client node. are there any changes in the utility command parameters in new version?  prior to upgrade it was working fine

checked the permission and ownership of arscache/cache1 folder and everything seems correct as per IBM documentation.

parameters used in arsmaint command -cdrs

documents are not getting flushed from cache folder.

Thanks,
Mayank

[mayank81089]

Understood system is working as expected.

Cache expiration is run using the arsmaint -c command.
OnDemand will expire storage objects from cache if all of the following conditions are met:
The maximum cache threshold is reached for a cache file system. This is specified when you run arsmaint with the '-x' parameter. The default value is 80%.

[Ed_Arnold]

mayank - are you good now?

Ed Arnold