Question & Answer
Question
When using IBM® Content Manager OnDemand server with application groups and storage sets defined for cache only, Tivoli Storage Manager only, or both cache and Tivoli Storage Manager storage, you notice document data is not consistently being expired. In what situations will Content Manager OnDemand expire or delete document data from Content Manager OnDemand cache and Tivoli Storage Manager (TSM) storage?
Answer
In most cases, each load in Content Manager OnDemand creates one or more internal storage objects. These storage objects contain the actual document data.
Content Manager OnDemand attempts to expire a storage object from Content Manager OnDemand cache in the following situations:
Content Manager OnDemand attempts to expire a storage object from TSM in the following situations:
If Data Retention Protection is enabled in TSM, Content Manager OnDemand expires objects in the following situations:
To determine the object expiration policy of your TSM archive copy group, run the following command:
Content Manager OnDemand attempts to expire a storage object from Content Manager OnDemand cache in the following situations:
- If an application group is deleted.
All storage objects in the application group are immediately deleted from Content Manager OnDemand cache. - If an arsadmin unload command is issued.
It will delete the load from Content Manager OnDemand cache. A load consists of document index values from the database and storage objects from storage. - Cache expiration is run using the arsmaint -c command.
Content Manager 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%.
- Cache Document Data for X days configuration in the application group has been met.
- If the storage object has been configured to migrate to TSM and has successfully been migrated.
Note: If a TSM storage node was added to an application group's storage set at a later time, previously loaded data in Content Manager OnDemand cache will not be migrated to TSM and will qualify for expiration. - Arsmaint does not encounter an error during expiration processing. If an error is encountered, the error must be corrected before cache expiration can continue. Run cache validation (arsmaint -v) and review the Content Manager OnDemand System Log for cache errors.
- Index expiration is run using the arsmaint -d command.
If the application group is configured as Expiration Type of Load, Content Manager OnDemand expires a load at a time based on the Life of Data and Indexes retention period that is configured in the application group. A load consists of index values that are inserted into the Content Manager OnDemand database and storage objects in Content Manager OnDemand cache and TSM.
Content Manager OnDemand attempts to expire a storage object from TSM in the following situations:
- If an application group is deleted.
Content Manager OnDemand immediately sends a DELETE FILESPACE command to TSM, that deletes all storage objects that are archived in TSM under this application group. - Index expiration is run using the arsmaint -d command.
If the application group is configured as Expiration Type of Load, Content Manager OnDemand deletes a load at a time based on the Life of Data and Indexes retention period that is configured in the application group. A load consists of index values that are inserted into the Content Manager OnDemand database and storage objects in Content Manager OnDemand cache and TSM. Content Manager OnDemand issues the TSM Client API, dsmDeleteObj, to delete storage objects in this scenario. - If an arsadmin unload command is issued.
This command deletes a load from Content Manager OnDemand in the same manner as the previous condition. - A matching AFP resource is found in TSM when loading data.
Content Manager OnDemand archives AFP resource and document data separately. If the load data contains AFP resources which match those that are already archived in TSM, Content Manager OnDemand archives the most recent copy and deletes the previous matching AFP resource object in TSM. This ensures that the AFP resource and document data has the same archive date and retention period in TSM. The TSM Client API, dsmDeleteObj, is also used in this scenario.
If Data Retention Protection is enabled in TSM, Content Manager OnDemand expires objects in the following situations:
- Data Retention Protection On
Creation-based object expiration
Content Manager OnDemand issues no commands to TSM. The objects are effectively orphaned by Content Manager OnDemand and are expired by TSM based on their retention parameters. If the retention parameters are set to NOLIMIT, then the objects never expire.
Event-based object expiration
Content Manager OnDemand issues an event trigger command through the TSM Client API. The event status of the objects that are affected are changed from PENDING to STARTED and the objects will be expired by TSM based on their retention parameters. If the retention parameters are set to NOLIMIT, then the objects never expire. If an application group is being deleted, a DELETE FILESPACE cannot be used with DRP enabled, so the operation is treated the same as if a delete were indicated. The status of all the affected objects is changed from PENDING to STARTED, and they will be expired by TSM based on their retention parameters. Because this leaves the filespace entries in TSM, you must manually delete these entries when the filespace is empty (even with DRP enabled).
Data Retention Protection Off
Creation-based object expiration
Content Manager OnDemand issues a delete object command through the TSM Client API. Objects are deleted during the next inventory expiration. If an application group is being deleted, a DELETE FILESPACE command is issued instead and the objects are immediately deleted along with the file space.
Event-based object expiration
Content Manager OnDemand issues an event trigger command through the TSM Client API. The status of the objects that are affected are changed from PENDING to STARTED, and the objects are expired by TSM based on their retention parameters. If the retention parameters are set to NOLIMIT, then the objects never expire. If an application group is being deleted, a DELETE FILESPACE command is issued instead, and the objects are immediately deleted along with the filespace.
To determine the object expiration policy of your TSM archive copy group, run the following command:
- q copy t=a f=d
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPCD","label":"Content Manager OnDemand for Multiplatforms"},"ARM Category":[{"code":"a8m0z0000001gP1AAI","label":"technote"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
14 March 2024
UID
swg21206601