Chapter 10. Migration and expiring data and indexes 235
Turning off data retention protection
When you turn off data retention protection, the following descriptions explain what happens 
when you use the creation-based object expiration policy and the event-based retention 
object expiration policy:
/SM590000Creation-based object expiration policy: Content Manager OnDemand issues a delete 
object command through the Tivoli Storage Manager API. Objects are deleted during the 
next inventory expiration. If a Content Manager OnDemand application group is deleted, a 
delete filespace command is issued instead, and the objects are immediately deleted 
with the file space.
/SM590000Event-based retention object expiration policy: Content Manager OnDemand issues an 
event trigger command through the Tivoli Storage Manager API. The status of the 
objects that are affected changes from PENDING to STARTED, and the objects are expired by 
Tivoli Storage Manager based on their retention parameters. If the retention parameters 
are set to NOLIMIT, the objects never expire. If a Content Manager OnDemand application 
group is deleted, a delete filespace command is issued instead, and the objects are 
immediately deleted with the file space.
Turning on data retention protection
When you turn on data retention protection, the following descriptions explain what happens 
when you use creation-based object expiration policy and event-based retention object 
expiration policy:
/SM590000Creation-based object expiration policy: Content Manager OnDemand issues no 
commands to Tivoli Storage Manager. The objects are effectively orphaned by Content 
Manager OnDemand and are expired by Tivoli Storage Manager based on their retention 
parameters. If the retention parameters are set to NOLIMIT, the objects never expire.
/SM590000Event-based retention object expiration policy: Content Manager OnDemand issues an 
event trigger command through the Tivoli Storage Manager API. The event status of the 
objects that are affected is changed from PENDING to STARTED, and the affected objects 
are expired by Tivoli Storage Manager based on their retention parameters. If the retention 
parameters are set to NOLIMIT, the objects never expire. 
If a Content Manager OnDemand application group is deleted, a delete filespace 
command cannot be used with data retention protection; the operation is treated the same 
as though a delete is indicated. The status of all of the affected objects is changed from 
PENDING to STARTED, and the affected objects are expired by Tivoli Storage Manager 
based on their retention parameters. This action leaves the file space entries in Tivoli 
Storage Manager, so you must manually delete these entries when the file space is empty 
(even with data retention protection on).
Recommendations
Consider the following preferred practices when you work with data retention protection:
/SM590000Set up the application groups to expire by load.
/SM590000Define the Tivoli Storage Manager archive copy groups to be event-based, and retain data 
for 0 days.
/SM590000Run the Tivoli Storage Manager inventory expiration regularly to ensure that expired data 
is removed.